Baffling DNS Problem

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Woke up one morning to find that both my internet browsers (IE7 and Netscape
7.2) were not loading any web pages! Narrowed it down to a local DNS
problem. I am running Windows XP Home Edition SP2.

Here's what's been established:
- I can connect to websites with IP addresses but not by their DNS server
names (tested with google.ca and others)
- Same result when 'pinging'
- Network Diagnostics for Windows XP also states a DNS problem in the log
(see below for full log)
- cable modem and connections are all in perfect working order (IP and DNS
addresses are all okay from ISP point of view)
- internet connection works just fine when switched over to my MacBook
- no virus or spyware detected (my antivirus software is current with latest
virus defs and AutoProtect enabled, I also have Windows Defender and Spybot
for spyware detection)

Things I've tried:
- repairing/renewing IP address
- flushing DNS
- reinstalling network drivers
- removing Winsock/Winsock2 from Registry and re-installing Internet TCP/IP
Protocol
- System Restore
- deleting all temp Internet files, cookies and history

Unfortunately, that's the extent of what I know to try, all to no avail and
I have a feeling reinstalling IE7 isn't the answer because Netscape has the
same DNS error. How do I fix this problem without resorting to try
reinstalling Windows XP? HELP!

Network Diagnostics Log:
Last diagnostic run time: 06/09/07 22:11:05 DNS Client Diagnostic
DNS - Not a home user scenario

info Using Web Proxy: no
info Resolving name ok for (www.microsoft.com): no
No DNS servers

DNS failure

info Query [www.microsoft.com] against DNS Server 64.59.135.133, (Type =
0x1, Options = 0x10e8) returns 0x5b4
info Query [www.microsoft.com] against DNS Server 64.59.135.135, (Type =
0x1, Options = 0x10e8) returns 0x5b4
action Automated repair: Renew IP address
action Releasing the current IP address...
action Successfully released the current IP address
action Renewing the IP address...
action Successfully renewed the current IP address
info Query [www.microsoft.com] against DNS Server 64.59.135.133, (Type =
0x1, Options = 0x10e8) returns 0x5b4
info Query [www.microsoft.com] against DNS Server 64.59.135.135, (Type =
0x1, Options = 0x10e8) returns 0x5b4
info Redirecting user to support call



Gateway Diagnostic
Gateway

info The following proxy configuration is being used by IE: Automatically
Detect Settings:Enabled Automatic Configuration Script: Proxy Server: Proxy
Bypass list:
info Could not get proxy settings via the Automatic Proxy Configuration
mechanism
info This computer has the following default gateway entry(ies): 70.72.37.1
info This computer has the following IP address(es): 70.72.37.150
info The default gateway is in the same subnet as this computer
info The default gateway entry is a valid unicast address
info The default gateway address was resolved via ARP in 1 try(ies)
info The default gateway was reached via ICMP Ping in 1 try(ies)
warn Hostname www.microsoft.com could not be resolved (Error code 0x2afc).
Could be either gateway or DNS issue
action Automated repair: Renew IP address
action Releasing the current IP address...
action Successfully released the current IP address
action Renewing the IP address...
action Successfully renewed the current IP address
info This computer has the following default gateway entry(ies): 70.72.37.1
info This computer has the following IP address(es): 70.72.37.150
info The default gateway is in the same subnet as this computer
info The default gateway entry is a valid unicast address
info The default gateway address was resolved via ARP in 1 try(ies)
info The default gateway was reached via ICMP Ping in 1 try(ies)
warn Hostname www.microsoft.com could not be resolved (Error code 0x2afc).
Could be either gateway or DNS issue
action Automated repair: Reset network connection
action Disabling the network adapter
action Enabling the network adapter
info Network adapter successfully enabled
info This computer has the following default gateway entry(ies): 70.72.37.1
info This computer has the following IP address(es): 70.72.37.150
info The default gateway is in the same subnet as this computer
info The default gateway entry is a valid unicast address
warn The default gateway address could not be resolved via ARP
action Manual repair: Reboot modem
info This computer has the following default gateway entry(ies): 70.72.37.1
info This computer has the following IP address(es): 70.72.37.150
info The default gateway is in the same subnet as this computer
info The default gateway entry is a valid unicast address
info The default gateway address was resolved via ARP in 1 try(ies)
info The default gateway was reached via ICMP Ping in 1 try(ies)
warn Hostname www.microsoft.com could not be resolved (Error code 0x2afc).
Could be either gateway or DNS issue
info Waiting some time for the modem/router to stabilize
action Automated repair: Renew IP address
action Releasing the current IP address...
action Successfully released the current IP address
action Renewing the IP address...
action Successfully renewed the current IP address
info This computer has the following default gateway entry(ies): 70.72.37.1
info This computer has the following IP address(es): 70.72.37.150
info The default gateway is in the same subnet as this computer
info The default gateway entry is a valid unicast address
info The default gateway address was resolved via ARP in 1 try(ies)
info The default gateway was reached via ICMP Ping in 1 try(ies)
warn Hostname www.microsoft.com could not be resolved (Error code 0x2afc).
Could be either gateway or DNS issue



IP Layer Diagnostic
Corrupted IP routing table

info The default route is valid
info The loopback route is valid
info The local host route is valid
info The local subnet route is valid
Invalid ARP cache entries

action The ARP cache has been flushed



IP Configuration Diagnostic
Invalid IP address

info Valid IP address detected: 70.72.37.150



Wireless Diagnostic
Wireless - Service disabled

Wireless - User SSID

Wireless - First time setup

Wireless - Radio off

Wireless - Out of range

Wireless - Hardware issue

Wireless - Novice user

Wireless - Ad-hoc network

Wireless - Less preferred

Wireless - 802.1x enabled

Wireless - Configuration mismatch

Wireless - Low SNR




WinSock Diagnostic
WinSock status

info All base service provider entries are present in the Winsock catalog.
info The Winsock Service provider chains are valid.
info Provider entry MSAFD Tcpip [TCP/IP] passed the loopback communication
test.
info Provider entry MSAFD Tcpip [UDP/IP] passed the loopback communication
test.
info Provider entry RSVP UDP Service Provider passed the loopback
communication test.
info Provider entry RSVP TCP Service Provider passed the loopback
communication test.
info Connectivity is valid for all Winsock service providers.



Network Adapter Diagnostic
Network location detection

info Using home Internet connection
Network adapter identification

info Network connection: Name=Local Area Connection, Device=Intel(R) PRO/100
VE Network Connection, MediaType=LAN, SubMediaType=LAN
info Network connection: Name=1394 Connection, Device=1394 Net Adapter,
MediaType=LAN, SubMediaType=1394
info Ethernet connection selected
Network adapter status

info Network connection status: Connected



HTTP, HTTPS, FTP Diagnostic
HTTP, HTTPS, FTP connectivity

warn FTP (Passive): Error 12007 connecting to ftp.microsoft.com: The server
name or address could not be resolved
warn HTTP: Error 12007 connecting to www.microsoft.com: The server name or
address could not be resolved
warn HTTPS: Error 12007 connecting to www.microsoft.com: The server name or
address could not be resolved
warn HTTPS: Error 12007 connecting to www.passport.net: The server name or
address could not be resolved
warn HTTP: Error 12007 connecting to www.hotmail.com: The server name or
address could not be resolved
warn FTP (Active): Error 12007 connecting to ftp.microsoft.com: The server
name or address could not be resolved
error Could not make an HTTP connection.
error Could not make an HTTPS connection.
error Could not make an FTP connection.
 
- no virus or spyware detected (my antivirus software is current with
latest
virus defs and AutoProtect enabled, I also have Windows Defender and
Spybot
for spyware detection)
Click to expand...

Details of this software? I've seen so many problems with software
firewalls, etc. that I'd bet money that this is where the problem is.

After then, I'd suspect issues with your NIC drivers.
 
mvp23 said:
Woke up one morning to find that both my internet browsers (IE7 and Netscape
7.2) were not loading any web pages! Narrowed it down to a local DNS
problem. I am running Windows XP Home Edition SP2.

Here's what's been established:
- I can connect to websites with IP addresses but not by their DNS server
names (tested with google.ca and others)
- Same result when 'pinging'
- Network Diagnostics for Windows XP also states a DNS problem in the log
(see below for full log)
- cable modem and connections are all in perfect working order (IP and DNS
addresses are all okay from ISP point of view)
- internet connection works just fine when switched over to my MacBook
- no virus or spyware detected (my antivirus software is current with latest
virus defs and AutoProtect enabled, I also have Windows Defender and Spybot
for spyware detection)

Things I've tried:
- repairing/renewing IP address
- flushing DNS
- reinstalling network drivers
- removing Winsock/Winsock2 from Registry and re-installing Internet TCP/IP
Protocol
- System Restore
- deleting all temp Internet files, cookies and history

Unfortunately, that's the extent of what I know to try, all to no avail and
I have a feeling reinstalling IE7 isn't the answer because Netscape has the
same DNS error. How do I fix this problem without resorting to try
reinstalling Windows XP? HELP!

Network Diagnostics Log:
Last diagnostic run time: 06/09/07 22:11:05 DNS Client Diagnostic
DNS - Not a home user scenario

info Using Web Proxy: no
info Resolving name ok for (www.microsoft.com): no
No DNS servers

DNS failure

info Query [www.microsoft.com] against DNS Server 64.59.135.133, (Type =
0x1, Options = 0x10e8) returns 0x5b4
info Query [www.microsoft.com] against DNS Server 64.59.135.135, (Type =
0x1, Options = 0x10e8) returns 0x5b4
action Automated repair: Renew IP address
action Releasing the current IP address...
action Successfully released the current IP address
action Renewing the IP address...
action Successfully renewed the current IP address
info Query [www.microsoft.com] against DNS Server 64.59.135.133, (Type =
0x1, Options = 0x10e8) returns 0x5b4
info Query [www.microsoft.com] against DNS Server 64.59.135.135, (Type =
0x1, Options = 0x10e8) returns 0x5b4
info Redirecting user to support call



Gateway Diagnostic
Gateway

info The following proxy configuration is being used by IE: Automatically
Detect Settings:Enabled Automatic Configuration Script: Proxy Server: Proxy
Bypass list:
info Could not get proxy settings via the Automatic Proxy Configuration
mechanism
info This computer has the following default gateway entry(ies): 70.72.37.1
info This computer has the following IP address(es): 70.72.37.150
info The default gateway is in the same subnet as this computer
info The default gateway entry is a valid unicast address
info The default gateway address was resolved via ARP in 1 try(ies)
info The default gateway was reached via ICMP Ping in 1 try(ies)
warn Hostname www.microsoft.com could not be resolved (Error code 0x2afc).
Could be either gateway or DNS issue
action Automated repair: Renew IP address
action Releasing the current IP address...
action Successfully released the current IP address
action Renewing the IP address...
action Successfully renewed the current IP address
info This computer has the following default gateway entry(ies): 70.72.37.1
info This computer has the following IP address(es): 70.72.37.150
info The default gateway is in the same subnet as this computer
info The default gateway entry is a valid unicast address
info The default gateway address was resolved via ARP in 1 try(ies)
info The default gateway was reached via ICMP Ping in 1 try(ies)
warn Hostname www.microsoft.com could not be resolved (Error code 0x2afc).
Could be either gateway or DNS issue
action Automated repair: Reset network connection
action Disabling the network adapter
action Enabling the network adapter
info Network adapter successfully enabled
info This computer has the following default gateway entry(ies): 70.72.37.1
info This computer has the following IP address(es): 70.72.37.150
info The default gateway is in the same subnet as this computer
info The default gateway entry is a valid unicast address
warn The default gateway address could not be resolved via ARP
action Manual repair: Reboot modem
info This computer has the following default gateway entry(ies): 70.72.37.1
info This computer has the following IP address(es): 70.72.37.150
info The default gateway is in the same subnet as this computer
info The default gateway entry is a valid unicast address
info The default gateway address was resolved via ARP in 1 try(ies)
info The default gateway was reached via ICMP Ping in 1 try(ies)
warn Hostname www.microsoft.com could not be resolved (Error code 0x2afc).
Could be either gateway or DNS issue
info Waiting some time for the modem/router to stabilize
action Automated repair: Renew IP address
action Releasing the current IP address...
action Successfully released the current IP address
action Renewing the IP address...
action Successfully renewed the current IP address
info This computer has the following default gateway entry(ies): 70.72.37.1
info This computer has the following IP address(es): 70.72.37.150
info The default gateway is in the same subnet as this computer
info The default gateway entry is a valid unicast address
info The default gateway address was resolved via ARP in 1 try(ies)
info The default gateway was reached via ICMP Ping in 1 try(ies)
warn Hostname www.microsoft.com could not be resolved (Error code 0x2afc).
Could be either gateway or DNS issue



IP Layer Diagnostic
Corrupted IP routing table

info The default route is valid
info The loopback route is valid
info The local host route is valid
info The local subnet route is valid
Invalid ARP cache entries

action The ARP cache has been flushed



IP Configuration Diagnostic
Invalid IP address

info Valid IP address detected: 70.72.37.150



Wireless Diagnostic
Wireless - Service disabled

Wireless - User SSID

Wireless - First time setup

Wireless - Radio off

Wireless - Out of range

Wireless - Hardware issue

Wireless - Novice user

Wireless - Ad-hoc network

Wireless - Less preferred

Wireless - 802.1x enabled

Wireless - Configuration mismatch

Wireless - Low SNR




WinSock Diagnostic
WinSock status

info All base service provider entries are present in the Winsock catalog.
info The Winsock Service provider chains are valid.
info Provider entry MSAFD Tcpip [TCP/IP] passed the loopback communication
test.
info Provider entry MSAFD Tcpip [UDP/IP] passed the loopback communication
test.
info Provider entry RSVP UDP Service Provider passed the loopback
communication test.
info Provider entry RSVP TCP Service Provider passed the loopback
communication test.
info Connectivity is valid for all Winsock service providers.



Network Adapter Diagnostic
Network location detection

info Using home Internet connection
Network adapter identification

info Network connection: Name=Local Area Connection, Device=Intel(R) PRO/100
VE Network Connection, MediaType=LAN, SubMediaType=LAN
info Network connection: Name=1394 Connection, Device=1394 Net Adapter,
MediaType=LAN, SubMediaType=1394
info Ethernet connection selected
Network adapter status

info Network connection status: Connected



HTTP, HTTPS, FTP Diagnostic
HTTP, HTTPS, FTP connectivity

warn FTP (Passive): Error 12007 connecting to ftp.microsoft.com: The server
name or address could not be resolved
warn HTTP: Error 12007 connecting to www.microsoft.com: The server name or
address could not be resolved
warn HTTPS: Error 12007 connecting to www.microsoft.com: The server name or
address could not be resolved
warn HTTPS: Error 12007 connecting to www.passport.net: The server name or
address could not be resolved
warn HTTP: Error 12007 connecting to www.hotmail.com: The server name or
address could not be resolved
warn FTP (Active): Error 12007 connecting to ftp.microsoft.com: The server
name or address could not be resolved
error Could not make an HTTP connection.
error Could not make an HTTPS connection.
error Could not make an FTP connection.
Click to expand...
But for your statement that things work OK with your MACBook, it might
be a problem with your ISPs DNS server. Just to be complete, try
setting the IP for the DNS server to some public DNS server:
http://www.tech-faq.com/public-dns-servers.shtml

How to configure TCP/IP to use DNS in Windows XP
http://support.microsoft.com/kb/305553/en-us
 
LEM:
I followed your advice on using Public DNS servers and tried several of
them. The result was that most web pages loaded but it was painfully slow.
Some still did not load at all.

Do you think it is a direct problem with my ISP's DNS server that is
obtained automatically (for your reference they are 64.59.135.133 and
64.59.135.135)? Or is it a problem with how my computer is communicating
with those particular DNS servers? FYI, when I run Network Diagnostics with
Windows XP again, this time it does NOT detect any problems with the
connection.

I will call my ISP again to see what they can do but if it's still a problem
on my end, what else can I try?

Thanks for your help.
 
LEM:
I followed your advice on using Public DNS servers and tried several of
them. The result was that most web pages loaded but it was painfully slow.
Some still did not load at all.

Do you think it is a direct problem with my ISP's DNS server that is
obtained automatically (for your reference they are 64.59.135.133 and
64.59.135.135)? Or is it a problem with how my computer is communicating
with those particular DNS servers? FYI, when I run Network Diagnostics with
Windows XP again, this time it does NOT detect any problems with the
connection.

I will call my ISP again to see what they can do but if it's still a problem
on my end, what else can I try?

Thanks for your help.
Click to expand...

Pick a public DNS server that's close to you. For any prospective server, do a
traceroute to that server and pick one with few hops. Your ISPs servers are
best, because well designed IPSs will have them at 0 hops. Less hops = less
latency.
 
mvp23 said:
LEM:
I followed your advice on using Public DNS servers and tried several of
them. The result was that most web pages loaded but it was painfully slow.
Some still did not load at all.

Do you think it is a direct problem with my ISP's DNS server that is
obtained automatically (for your reference they are 64.59.135.133 and
64.59.135.135)? Or is it a problem with how my computer is communicating
with those particular DNS servers? FYI, when I run Network Diagnostics with
Windows XP again, this time it does NOT detect any problems with the
connection.

I will call my ISP again to see what they can do but if it's still a problem
on my end, what else can I try?

Thanks for your help.
Click to expand...

I'm not sure what to suggest. Assuming that there is not, in fact, a
problem with your ISP's DNS servers, it seems as if you are blocked from
connecting to those IP addresses. It's sort of like a hosts file issue,
except the hosts file doesn't re-direct IP addresses to other IP
addresses (just domain names to other IP addresses). Do you connect to
the Internet through a proxy server? A router?

Can you ping 64.59.135.133 and 64.59.135.135? Check to see that you
don't have any firewall (or "Internet Worm Protection") that might be
blocking these addresses. You might also, on general principals, to a
thorough malware check, using at least a couple of different
applications. See
http://www.elephantboycomputers.com/page2.html#Removing_Malware for
suggestions.
 
No proxy or router. I will play around with the Windows XP firewall settings
(the only firewall I know that is active on my computer) and also try
checking further for Malware. I don't have time to do all that this week so
I'll post an update next week.

I am starting to think that maybe I WAS hacked through Malware or
otherwise... things just don't add up with it happening overnight and the
fact that the same ISP connection/DNS works fine on my laptop.
 
I have the same problem and have done everything that you have AND install SP3.

I did observe that NSLOOKUP will resolve google.com or microsoft.com, but it will not resolve www.google.com of www.microsoft.com. An internet browser will not navigate to any of these addresses, but will go to an IP address that was obtained by a NSLOOKUP.

How about you?

I also observed that when I tried to nslookup www.google.com, it was appeded with my ISP DNS suffix.

I did mess with the DNS suffix settings in the IP network configuration and observed a change for a moment when www.google.com resolved to www.l.google.com. Then the problem returned.
 
Back
Top