OpenDNS Forums
The official support and discussion site of OpenDNS
Support
K-12 Forums
Categories
- Administrative
- Adult site blocking
- DNS-O-Matic / dynamic IPs
- Domain blocking
- Domain Name System (DNS) troubles
- Mobile instructions
- OpenDNS services
- Proxies, accelerators, and more
- Router instructions
- Satellite
- Shortcuts
- Wishlists and feature requests
-
Feeds
Vanilla 1.1.4 is a product of Lussumo. More Information: Documentation, Community Support.
This discussion has been inactive for longer than 30 days, and is thus closed.
Domain Name System (DNS) troubles: Failure to communicate - please help
Bottom of Page1 to 17 of 17
-
Hi, I hope you can help with my problem...
I've had DNS issues for a long time now my home computer. I share a wired router with other family members and their PCs (as in, we plug the ethernet into the currently required PC as needed). Nobody else has any issues with connection, leading me to believe it's something about the settings on my computer. I would connect, then disconnect, then at some point reconnect randomly, before disconnecting again. Diagnosing the problem during the disconnects would present the error message "There may be a problem with your DNS configuration."
So I came across OpenDNS. I set it all up for my computer and it connected. Great, right? =( Unfortunately not. Minutes later I couldn't access the Internet, although I didn't actually disconnect. When this happens I am now presented with the error message "Failed to communicate with Primary DNS Server(208.67.222.222)".
What can the problem be? Why is it just my computer it happens on? Please can anybody help me I'm really sick and tired of DNS! -
- CommentAuthormaintenance
- CommentTimeJun 30th 2009
It would be you local dns, not internet dns which is the problem (if it is, in fact, the problem). When you say, "disconnects", what is disconnecting? Are you losing the connection to the router or the internet?
Please post the output of ipconfig /all from the problem computer here. -
Now that you mention it, it's the router I'm losing connection to - but as I say nobody else who uses the router is having this issue so... I'd be hesitant to mess with any router settings.
IPCONFIG /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : Dwain-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mshome.net
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : mshome.net
Description . . . . . . . . . . . : Realtek RTL8101E Family PCI-E Fast Ethern
et NIC (NDIS 6.0)
Physical Address. . . . . . . . . : 00-1B-38-4B-2E-A0
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::a06b:e556:2147:16a6%9(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.5(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 01 July 2009 16:25:15
Lease Expires . . . . . . . . . . : 02 July 2009 16:25:15
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 201333560
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-0F-50-D6-6C-00-1B-38-4B-2E-A0
DNS Servers . . . . . . . . . . . : fe80::2481:bbdd:6395:15fc%9
208.67.222.222
208.67.220.220
NetBIOS over Tcpip. . . . . . . . : Enabled
Connection-specific DNS Suffix Search List :
mshome.net
Tunnel adapter Local Area Connection* 6:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 10:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : mshome.net
Description . . . . . . . . . . . : isatap.{D4FFCA38-201A-410B-9697-254BEDA62
19E}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 14:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 6TO4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes -
Is your computer the only place where the OpenDNS server addresses are configured? Or are these configured on the router as well?
Also, I would recommend to remove this DNS suffix stuff (mshome.net) from the TCP/IP settings of your NIC configuration.
Now post the output of the following commands:
nslookup www.opendns.com. 208.67.222.222
nslookup www.opendns.com. 208.67.220.220
nslookup www.opendns.com.
Edit: Sorry, corrected above from "Is your router the only place..."
-
I think you meant computer, but you said router? But the OpenDNS stuff is just configured on my computer, not the router. Does it have to be both? I'm wary about fiddling with this because, as I say, the router works perfect for other computers...
I'm afraid I don't know how to remove the DNS Suffix thing :/
Output stuff:
C:\Users\DwainW>nslookup www.opendns.com 208.67.222.222
Server: resolver1.opendns.com
Address: 208.67.222.222
Non-authoritative answer:
Name: www.opendns.com
Address: 208.67.219.101
C:\Users\DwainW>nslookup www.opendns.com 208.67.220.220
Server: resolver2.opendns.com
Address: 208.67.220.220
Non-authoritative answer:
Name: www.opendns.com
Address: 208.67.219.101
C:\Users\DwainW>nslookup www.opendns.com
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: fe80::2481:bbdd:6395:15fc
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out -
- CommentAuthorinfinity306
- CommentTimeJul 1st 2009
You missed the . on them .. should be nslookup www.opendns.com.
Although the results do seem to point that you are using opendns and that your ISP is not restricting DNS traffic to it's own servers..
Hmm results #3 is bad.. change your computer to point to Opendns servers as DNS servers not IPV6 addresses... -
- CommentAuthorinfinity306
- CommentTimeJul 1st 2009
For a home setup, I'd also suggest upping your DHCP Timeout from 24 hours.. while the DHCP timeout being only 24 hours wont hurt, in a home setting unless you have a very narrow DHCP scope, you shouldn't need to refresh that often.. -
- CommentAuthorinfinity306
- CommentTimeJul 1st 2009
here's your problem.....
DNS Servers . . . . . . . . . . . : fe80::2481:bbdd:6395:15fc%9
208.67.222.222
208.67.220.220
Either make the IPv6 address the last address or remove it completely..Thankful People: kuraidark -
@kuraidark
"Does it have to be both? ? I'm wary about fiddling with this..."
No, far not, not on both at the same time please! If you want to have OpenDNS just on your computer, your current approach is perfect!
Now commenting your command outputs:
nslookup www.opendns.com 208.67.222.222
nslookup www.opendns.com 208.67.220.220
This looks good, both returns 208.67.219.101, which indicates that you can reach OpenDNS for DNS lookups. It is not blocked or redirected yet, e.g. by the router or by your ISP.
However, as @infinity306 mentioned, you missed the trailing dot after .com, but this didn't matter in this case.
nslookup www.opendns.com
Again, the missing trailing dot, and also, the result is horrifying. It fully explains why you got the impression "Minutes later I couldn't access the Internet, although I didn't actually disconnect". In fact you were still connected, but losing DNS looks like you lost the internet connection...
Now you know how important this "internet phonebook" DNS in general is!
Unlike @infinity306 advices, I would not know a method under Vista to change the order of IPv6 DNS server entries against IPv4 DNS server entries, because these are configured in different areas. (Maybe with netsh? But this is nothing for an unexperienced user...) It seems to be a Vista bug. Vista should not try to resolve first via IPv6, or, if not successful via IPv6, it should attempt with IPv4 then. Apparently this is not the case. You may search the internet if you find a solution for this. However, as you do not seem to use IPv6 connectivity at all yet, you simply can deactivate or even uninstall IPv6.
At the same occasion you can probably remove the DNS suffix stuff, as it is close nearby, both near the place where you entered the OpenDNS server addresses.
To remove IPv6 connectivity go to http://www.opendns.com/img/start_vista6a.gif
From the list select "Internet Protocol Version 6 (TCP/IPv6)", and either deactivate the checkbox or click Uninstall, before you confirm "Ok".
To look for DNS suffixes go to http://www.opendns.com/img/start_vista7a.gif
Then click Advanced and go to the DNS tab. There you find several radio buttons and check boxes and a list box, all for DNS suffix stuff. Remove and deactivate everything, as far as possible.
And yes, as @infinity306 wrote, you may increase the DHCP lease time at this occasion as well, e.g. to a week or even a month. You probably have to set this on your router, if this supports to change this parameter, because I do not know a place in Vista, where the lease time could be changed. Does anybody else know?
Edit: If you need more orientation because of the pictures above, these have been taken from https://www.opendns.com/start/device/windows-vistaThankful People: kuraidark -
- CommentAuthorinfinity306
- CommentTimeJul 1st 2009 edited
No I believe DHCP Lease time is only at DHCP server level and not configurable at Computer level, which would be on the router.. for some reason on many routers 24 hours seems to be the default when in most cases on a router 24 hours is unnecessarily short. did you just recently upgrade to Vista SP2?
Hmm interesting.. I just tried adding IPv6 to Xp SP3 using Netsh interface add.. and it added the teredo tunneling Psuedo-Interface but added IPv6 DNS servers at the bottom of the list of DNS servers and works correctly at least for NSlookup..
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Controller
Physical Address. . . . . . . . . : 00-13-72-89-46-92
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.198
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::213:72ff:fe89:4692%5
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.4
192.168.1.254
fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
Lease Obtained. . . . . . . . . . : Wednesday, July 01, 2009 9:58:59 AM
Lease Expires . . . . . . . . . . : Wednesday, July 15, 2009 9:58:59 AM
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%4
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter Automatic Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Automatic Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : C0-A8-00-C6
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:192.168.0.198%2
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled -
Yes, I can confirm this. This is mine. (Sorry, it's in German.)
Note that I always delete the "Teredo Tunneling Pseudo-Interface" at startup time with netsh. Beside this, you are seeing here true IPv6 connectivity via a tunnel "in action".
Windows-IP-Konfiguration
Hostname. . . . . . . . . . . . . : doesntmatter
Primäres DNS-Suffix . . . . . . . :
Knotentyp . . . . . . . . . . . . : Unbekannt
IP-Routing aktiviert. . . . . . . : Nein
WINS-Proxy aktiviert. . . . . . . : Nein
Ethernetadapter Drahtlose Netzwerkverbindung:
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Wireless 802.11b/g 54Mbps USB 2.0
Physikalische Adresse . . . . . . : 00-18-E7-0D-CB-7A
DHCP aktiviert. . . . . . . . . . : Nein
IP-Adresse. . . . . . . . . . . . : 192.168.2.11
Subnetzmaske. . . . . . . . . . . : 255.255.255.0
IP-Adresse. . . . . . . . . . . . : fe80::218:e7ff:fe0d:cb7a%5
Standardgateway . . . . . . . . . : 192.168.2.1
DNS-Server. . . . . . . . . . . . : 192.168.2.1
fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
Tunneladapter Automatic Tunneling Pseudo-Interface:
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Automatic Tunneling Pseudo-Interface
Physikalische Adresse . . . . . . : C0-A8-02-0B
DHCP aktiviert. . . . . . . . . . : Nein
IP-Adresse. . . . . . . . . . . . : fe80::5efe:192.168.2.11%2
Standardgateway . . . . . . . . . : ::216.66.80.30
DNS-Server. . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS über TCP/IP . . . . . . . : Deaktiviert
ping ipv6.google.com
Ping ipv6.l.google.com [2001:4860:a005::68] mit 32 Bytes Daten:
Antwort von 2001:4860:a005::68: Zeit=22ms
Antwort von 2001:4860:a005::68: Zeit=21ms
Antwort von 2001:4860:a005::68: Zeit=20ms
Antwort von 2001:4860:a005::68: Zeit=20ms
Ping-Statistik für 2001:4860:a005::68:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 20ms, Maximum = 22ms, Mittelwert = 20ms
nslookup -type=aaaa ipv6.google.com.
Server: speedport.ip
Address: 192.168.2.1
Nicht autorisierte Antwort:
ipv6.google.com canonical name = ipv6.l.google.com
ipv6.l.google.com AAAA IPv6 address = 2001:4860:a005::68
tracert ipv6.google.com
Routenverfolgung zu ipv6.l.google.com [2001:4860:a005::68] über maximal 30 Abschnitte:
1 13 ms 12 ms 12 ms rotblitz1-3.tunnel.tserv6.fra1.ipv6.he.net [2001:470:1f0a:14d0::1]
2 9 ms 12 ms 12 ms gige-g2-4.core1.fra1.he.net [2001:470:0:69::1]
3 13 ms 10 ms 11 ms de-cix20.net.google.com [2001:7f8::3b41:0:1]
4 * * * Zeitüberschreitung der Anforderung.
5 * * * Zeitüberschreitung der Anforderung.
6 * * * Zeitüberschreitung der Anforderung.
7 24 ms 23 ms 21 ms ey-in-x68.google.com [2001:4860:a005::68]
Ablaufverfolgung beendet. -
Thank you guys this is very useful! I'll look into the stuff you've recommended now and let you know =)
-
Okay I've made the changes by deactivating IPv6 (I didn't uninstall in case something goes wrong and I need it back) and removing the DNS suffix stuff as far as I could............. Just as I was typing this I lost connectivity. /sigh
I think this problem might be insoluble!
Any more advice? No worries if not I'll just have to live with it! Here's the latest ipconfig:
Windows IP Configuration
Host Name . . . . . . . . . . . . : Dwain-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8101E Family PCI-E Fast Ethern
et NIC (NDIS 6.0)
Physical Address. . . . . . . . . : 00-1B-38-4B-2E-A0
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.5(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 02 July 2009 11:30:39
Lease Expires . . . . . . . . . . : 03 July 2009 11:30:38
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 208.67.222.222
208.67.220.220
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Local Area Connection* 6:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 10:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{D4FFCA38-201A-410B-9697-254BEDA62
19E}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 14:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 6TO4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes -
- CommentAuthorinfinity306
- CommentTimeJul 2nd 2009 edited
can you post the output of nslookup www.opendns.com. post disabling of IPv6?
Also try ipconfig /flushdnsThankful People: kuraidark -
@kuraidark
"Just as I was typing this I lost connectivity."
Next time when this happens, can you visit http://208.67.219.60/ with your browser to see if you really lost connectivity, or just DNS.
Your TCP/IP config looks ideal now. It should work. If not, there must be a different cause.
Edit: And yes, do what @infinity306 is asking for.Thankful People: kuraidark -
C:\Users\DwainW>ipconfig /flushdns
Windows IP Configuration
Successfully flushed the DNS Resolver Cache.
C:\Users\DwainW>nslookup www.opendns.com.
Server: resolver1.opendns.com
Address: 208.67.222.222
Non-authoritative answer:
Name: www.opendns.com
Address: 208.67.219.101
And I tried http://208.67.219.60/ during a disconnect and just got an IE error page.
/sigh -
- CommentAuthorinfinity306
- CommentTimeJul 2nd 2009
Hmm, everything looks correct.. I wonder if there might be underlying hardware/ISP issues popping up that just happened to have weird timing..
Hmm another thought came to mind.. maybe the ethernet Cable has a flaw in it, and your computer is more sensitive to it then the other Family members? or maybe there is something wrong with the Network adapter/port on your computer? I have seen issues at work where 1 employee has a laptop that disconnects from the Server and goes offline a few times a day but no other employees are affected.. in that case I narrowed it down and Rolled the Network adapter driver back and it seems to have fixed that problem..
What IE Error page did you get?
1 to 17 of 17
This discussion has been inactive for longer than 30 days, and is thus closed.
