How to repair DNS?

  • Thread starter Thread starter Xorn
  • Start date Start date
X

Xorn

My Internet Connection is not working and I've diagnosed the problem is with
DNS, but can't seem to figure out how to repair. I searched this newsgroup
but did not see anything resembling my situation.

I can connnect to anything via ip but not by domain name.
Running Windows XP Pro with SP3.

Network Diagnostics for Windows XP shows: DNS failure

Confirmed this by successfully connecting two ways from a different computer
on my network.
ping www.yahoo.com
ping 69.147.76.15

But when I tried same test from problem computer
ping www.yahoo.com failed
ping 69.147.76.15 succeeded


One exception is that I *can* successfully ping local device names:
ping xp_pro_1 (host computer)
ping dlinkserver (router)


I've tried a number of "resets" but none have worked.
Some stuff I've tried:
ipconfig /flushdns
ipconfig /registerdns
netsh winsock reset
netsh int ip reset

Looking for a step by step guide on how to repair, or recommended software
utility that can fix it.
Any suggestions would be greatly appreciated!
 
Please post the output of ipconfig /all and information about the type of
connection. Using DHCP or static address? Using a router? Direct to DSL
modem? Cable modem? Other?
 
My Internet Connection is not working and I've diagnosed the
problem is with DNS, but can't seem to figure out how to repair.
I searched this newsgroup but did not see anything resembling my
situation.

I can connnect to anything via ip but not by domain name.
Running Windows XP Pro with SP3.

Network Diagnostics for Windows XP shows: DNS failure

Confirmed this by successfully connecting two ways from a
different computer on my network.
ping www.yahoo.com
ping 69.147.76.15

But when I tried same test from problem computer
ping www.yahoo.com failed
ping 69.147.76.15 succeeded


One exception is that I *can* successfully ping local device
names: ping xp_pro_1 (host computer)
ping dlinkserver (router)


I've tried a number of "resets" but none have worked.
Some stuff I've tried:
ipconfig /flushdns
ipconfig /registerdns
netsh winsock reset
netsh int ip reset

Looking for a step by step guide on how to repair, or recommended
software utility that can fix it.
Any suggestions would be greatly appreciated!
Click to expand...

A lot depends on how you connect to the internet but assuming a
standard DHCP-configured connection, check the following:

Control Panel -> Network Connections ->
Right-Click on your connection -> Properties
Scroll down in middle window, single click on TCP/IP (not checkbox)
-> Properties
Verify that "Obtain DNS Server Address Automatically" is checked.

As "GTS" stated, posting the output of an "ipconfig /all" command
would help us.

HTH,
John
 
Please post the output of ipconfig /all and information about the type of
connection. Using DHCP or static address? Using a router? Direct to DSL
modem? Cable modem? Other?
--
Click to expand...

Using standard DHCP. Using a D-Link router and DSL modem.
Other computers on the network connect with no issues.
ipconfig /all
Click to expand...

Windows IP Configuration

Host Name . . . . . . . . . . . . : xp_pro_1
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated
Con
roller
Physical Address. . . . . . . . . : 00-0B-DB-0E-8B-EB
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.191
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Sunday, June 21, 2009 10:05:45 AM
Lease Expires . . . . . . . . . . : Monday, June 22, 2009 10:05:45 AM

Ethernet adapter Wireless Network Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8185 54M Wireless LAN
Net
work Adapter
Physical Address. . . . . . . . . : 00-14-D1-34-21-44
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.189
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Sunday, June 21, 2009 10:17:58 AM
Lease Expires . . . . . . . . . . : Monday, June 22, 2009 10:17:58 AM
 
Confirmed that both
"Obtain DNS Server Address Automatically" is checked
and
"Obtain an IP address Automatically" is checked

ipconfig /all
Click to expand...

Windows IP Configuration

Host Name . . . . . . . . . . . . : xp_pro_1
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated
Con
roller
Physical Address. . . . . . . . . : 00-0B-DB-0E-8B-EB
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.191
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Sunday, June 21, 2009 10:05:45 AM
Lease Expires . . . . . . . . . . : Monday, June 22, 2009 10:05:45 AM

Ethernet adapter Wireless Network Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8185 54M Wireless LAN
Net
work Adapter
Physical Address. . . . . . . . . : 00-14-D1-34-21-44
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.189
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Sunday, June 21, 2009 10:17:58 AM
Lease Expires . . . . . . . . . . : Monday, June 22, 2009 10:17:58 AM
 
The ipconfig looks normal. The last few times I've seen a similar problem
it involved malware. Have you investigated that? I would particularly
recommend running MalwareBytes and SuperAntispyware. Also, are you using
any 3rd party firewall or security suite? You might also boot to safe mode
with networking and see if the same problem is present
--
 
Xorn said:
Confirmed that both
"Obtain DNS Server Address Automatically" is checked
and
"Obtain an IP address Automatically" is checked



Windows IP Configuration

Host Name . . . . . . . . . . . . : xp_pro_1
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated
Con
roller
Physical Address. . . . . . . . . : 00-0B-DB-0E-8B-EB
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.191
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Sunday, June 21, 2009 10:05:45
AM
Lease Expires . . . . . . . . . . : Monday, June 22, 2009 10:05:45
AM

Ethernet adapter Wireless Network Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8185 54M Wireless
LAN
Net
work Adapter
Physical Address. . . . . . . . . : 00-14-D1-34-21-44
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.189
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Sunday, June 21, 2009 10:17:58
AM
Lease Expires . . . . . . . . . . : Monday, June 22, 2009 10:17:58
AM
Click to expand...
The DNS Server seems to me to be wrong. It looks like that is the router
address, but I was not aware that routers do DNS serving.

My setup looks almost like the OP's, but the difference is that the DNS
Servers are way out there in ip land (well actually, they belong to the
ISP). If I remember correctly, I defined the DNS servers in the router.

Jim
 
Confirmed that both
"Obtain DNS Server Address Automatically" is checked
and
"Obtain an IP address Automatically" is checked



Windows IP Configuration
Click to expand...

[snip]

IP config looks OK.

My next guess at this point would be a Firewall blocking the DNS port
(Port 53). If you've recently installed or uninstalled a Firewall
program on your computer (or repaired malware), this would be suspect.
As a shot-in-the-dark, sometimes one of the following freebie programs
will repair problems like this.

LSPFix
<http://www.cexx.org/lspfix.htm>
Winsock XP Fix
<http://www.snapfiles.com/get/winsockxpfix.html>

HTH,
John
 
Thanks for all the suggestions, but I still have the same issue.
Any more ideas?

I installed and ran both Malwarebytes Anti-Malware and SUPERAntispyware.
These programs identified various infected files and objects, which I
removed, but that didn't fix things.

Ran "netsh interface ip delete arpcache" as well, but no improvement.

I don't believe problem is with the DNS server ip address as someone
suggested, because I have another computer that connects successfully to
internet using same DNS Servers ip:

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG
Networ
k Connection
Physical Address. . . . . . . . . : 00-1C-BF-3D-53-68
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.149
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Sunday, June 21, 2009 1:53:19 PM
Lease Expires . . . . . . . . . . : Monday, June 22, 2009 1:53:19 PM
 
Met this one before. I notice that your router is acting as a DNS relay:

DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1 <-

This is normally quite OK, BUT some models of router (especially D-Link
DSL504 with early firmware) will not relay DNS correctly to some ISP setups.
I would suggest you try using a DNS server at your ISP directly, bypassing
the router's DNS relay. If this turns out to cure the problem, a firmware
update may fix the router's DNS relayer. Or, you can just use manually-set
DNS on the computers.

The reason this started suddenly is likely because the ISP bought new DNS
equipment, which caused the router's bug to manifest itself. The problem,
when it occurs, is intermittent and hard to track-down.

Also, it's worthwhile to turn off the dnscache service. This is mainly of
help to dialup users, and can cause problems on BB.

net stop dnscache (or change setting in services.msc for permanent turn-off)
 
Back
Top