Reply
Initial Contributor
Posts: 1
Registered: ‎2011-11-14

router dropping DNS service

My WNDR4000 will run fine but will drop the DNS service intermittently. I can communicate with the router wired and wirelessly but cannot resolve http addresses. In the logs below show I can ping the a valid address - the first ping packet is dropped but the following packets succeed?

Current Firmware is V1.0.0.82_8.0.71
DNS set to get DNS from ISP (Comcast) automatically.

Don't suspect my ISP yet as I had a very stable connection prior to this router.

Got home from work today and the DNS had dropped again. I can go to Basic Setting and execute "Test" and that will restore the DNS (suppose that is a reboot).

Any ideas to resolve this would be greatly appreciated!

Here is a log prior to the reboot:
C:\Users\Michael>ipconfig

Windows IP Configuration


Wireless LAN adapter Wireless Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::95c9:6313:abe2:c5eb%10
IPv4 Address. . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1

Tunnel adapter isatap.{0580D151-CBFF-4A76-A6D9-1D30894C0C70}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter isatap.{3FACD630-552D-41E4-A070-10E5FFD5A325}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

**********************************
COMMENT: cannot resolve google address

C:\Users\Michael>ping www.google.com
Ping request could not find host www.google.com. Please check the name and try a
gain.

***************************
COMMENT: Didn't quite understand this - I can ping the address but it consistently will drop the first ping packet, while the other succeed??

C:\Users\Michael>ping 68.87.72.134

Pinging 68.87.72.134 with 32 bytes of data:
Request timed out.
Reply from 68.87.72.134: bytes=32 time=12ms TTL=59
Reply from 68.87.72.134: bytes=32 time=12ms TTL=59
Reply from 68.87.72.134: bytes=32 time=12ms TTL=59

Ping statistics for 68.87.72.134:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 12ms, Average = 12ms

C:\Users\Michael>ping 68.87.72.134

Pinging 68.87.72.134 with 32 bytes of data:
Request timed out.
Reply from 68.87.72.134: bytes=32 time=11ms TTL=59
Reply from 68.87.72.134: bytes=32 time=11ms TTL=59
Reply from 68.87.72.134: bytes=32 time=10ms TTL=59

Ping statistics for 68.87.72.134:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 11ms, Average = 10ms

C:\Users\Michael>ping 68.87.77.134

Pinging 68.87.77.134 with 32 bytes of data:
Request timed out.
Reply from 68.87.77.134: bytes=32 time=30ms TTL=57
Reply from 68.87.77.134: bytes=32 time=45ms TTL=57
Reply from 68.87.77.134: bytes=32 time=29ms TTL=57

Ping statistics for 68.87.77.134:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 45ms, Average = 34ms

***********************************
COMMENT: After the "Test" (reboot)

C:\Users\Michael>ping 68.87.77.134

Pinging 68.87.77.134 with 32 bytes of data:
Reply from 68.87.77.134: bytes=32 time=31ms TTL=57
Reply from 68.87.77.134: bytes=32 time=29ms TTL=57
Reply from 68.87.77.134: bytes=32 time=29ms TTL=57
Reply from 68.87.77.134: bytes=32 time=29ms TTL=57

Ping statistics for 68.87.77.134:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 31ms, Average = 29ms

C:\Users\Michael>ping www.google.com

Pinging www.l.google.com [74.125.225.19] with 32 bytes of data:
Reply from 74.125.225.19: bytes=32 time=10ms TTL=55
Reply from 74.125.225.19: bytes=32 time=13ms TTL=55
Reply from 74.125.225.19: bytes=32 time=17ms TTL=55
Reply from 74.125.225.19: bytes=32 time=14ms TTL=55

Ping statistics for 74.125.225.19:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 17ms, Average = 13ms


C:\Users\Michael>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Users\Michael>ipconfig

Windows IP Configuration


Wireless LAN adapter Wireless Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::95c9:6313:abe2:c5eb%10
IPv4 Address. . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1

Tunnel adapter isatap.{0580D151-CBFF-4A76-A6D9-1D30894C0C70}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fd:14d5:da1:bc52:ba9d
Link-local IPv6 Address . . . . . : fe80::14d5:da1:bc52:ba9d%11
Default Gateway . . . . . . . . . : ::

Tunnel adapter isatap.{3FACD630-552D-41E4-A070-10E5FFD5A325}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

C:\Users\Michael>
Discussion Stats
  • 0 replies
  • 1526 views
  • 0 kudos
  • 1 in conversation
Top Contributors