Constant DNS Errors!

I have been having major DNS issues since yesterday (8 April 2011). My connection was dropping roughly every 15 minutes over much of yesterday. Troubleshooting the problem was diagnosed each time as "The DNS server isn't responding". Sometimes the diagnostic result came up as "My computer is using DNS settings that don't exist" (or similar wording).

I had reset the router several times and went through all the basics of restarting my PC and flushing the DNS cache. But no sooner had the connection been re-established, then it was down again.

My DNS settings were set to automatically obtains DNS. Since the problems began I had started using OPEN DNS settings direct from Windows IPV4 settings, as opposed to changing the router settings.

Since doing all of the above the connection seemed to be quite stable for a short while, but now the same thing with regular drop outs has started happening again. I have not had any DNS problems previously (at least not on this scale). So I am just wondering why I have suddenly started to get these problems and what the resolve might be?

G'Day garyc,

Can you call support or PM with the details please.

Hello and thanks for your reply.

Strangely enough, since posting the above I have not had any further problems.
I have put the DNS settings back to "obtain DNS server address automatically" and since about midday on Saturday, I have had a continuous connection and no further problems.

Great news.

If you can, do keep me posted.

I have the same and previously posted this on an earlier thread.

It only occurs at peak times and the fault extracted from my console said

Apr 4 18:54:33 Macintosh configd[17]: IPMonitor: ignoring bad DNS server address ''
Apr 4 18:54:33 Macintosh configd[17]: network configuration changed.

These coincided with a complete refusal to pass data and only a reboot of the router was enough to get traffic flowing again.

It has been doing it continually but this week has not affected traffic in the last week = perhaps the holiday have changed patterns of use in the evenings.

All my computers go directly to the Zen DNS servers, as that has always given me a better connection.

Hi again, those dreaded DNS errors have returned again today. I have spoken to support and they confirm that my connection had dropped 63 times in last 24 hours.
It was working again when I came off the phone to support, but the connection is dropping again now every few minutes. The same error messages as in my original post.

I have tried everything I can think of including flushing the DNS cache, restarting the router, restarting the PC. Using the network trouble shooter always points to DNS errors and that "The primary DNS server is not responding"!

Edited by deleted (Fri 13-May-11 15:35:07)

you obviously have a problem tht is not going to go away.
What you need to do is to prepare some checks when the 'system' is working and when it is failed, re-run the checks to attempt to fins out just where the fault is.

I would:

1) Test ping to www.bbc.co.uk
2) Test ping to the IP address of www.bbc.co.uk, 212.58.244.68
3) Test ping to your router (192.168.x.x)??
4) Logon to your router's web interface usng xxx.xxx.xx.xxx?
5) Use the routers test ping to (1) above, discounts your pc
6) Use the routers test ping to (2) avove, discounts your pc. If this works, router DNS not working
7) Use router status screen to see current adsl status
8) anything else you can think of..

Disconnected

1) Test ping to www.bbc.co.uk

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Gary>ping www.bbc.co.uk
Ping request could not find host www.bbc.co.uk. Please check the name and try again

2) Test ping to the IP address of www.bbc.co.uk, 212.58.244.68

C:\Users\Gary>ping 212.58.244.68

Pinging 212.58.244.68 with 32 bytes of data:
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.

Ping statistics for 212.58.244.68:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

3) Test ping to your router (192.168.x.x)??

C:\Users\Gary>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

4) Logon to your router's web interface usng xxx.xxx.xx.xxx?

Done

5) Use the routers test ping to (1) above, discounts your pc

Can't ping names

6) Use the routers test ping to (2) avove, discounts your pc. If this works, router DNS not working

ping 212.58.244.68
Pkt_Sent:0 Pkt_Recv:0 Avg_Rtt:0ms

7) Use router status screen to see current adsl status

Firmware Version: V1.00.16
MAC Address: 00:1D:7E:B7:DE:C0
Current Time: 14-05-2011 08:12:24
Cisco Logo
Internet Connection

Login Type: RFC 2364 PPPoA
Interface: Down
IP Address: ---
Subnet Mask: ---
Default Gateway: ---
DNS 1: ---
DNS 2: ---
DNS 3: ---
WINS: ---


Connected

1) Test ping to www.bbc.co.uk

C:\Users\Gary>ping www.bbc.co.uk

Pinging www.bbc.net.uk [212.58.246.90] with 32 bytes of data:
Reply from 212.58.246.90: bytes=32 time=33ms TTL=57
Reply from 212.58.246.90: bytes=32 time=32ms TTL=57
Reply from 212.58.246.90: bytes=32 time=33ms TTL=57
Reply from 212.58.246.90: bytes=32 time=33ms TTL=57

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

2) Test ping to the IP address of www.bbc.co.uk, 212.58.244.68

C:\Users\Gary>ping 212.58.244.68

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

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

3) Test ping to your router (192.168.x.x)??

C:\Users\Gary>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

4) Logon to your router's web interface usng xxx.xxx.xx.xxx?

Done

5) Use the routers test ping to (1) above, discounts your pc

Can't ping names

6) Use the routers test ping to (2) avove, discounts your pc. If this works, router DNS not working

PING 212.58.244.68 (212.58.244.68) 60 bytes of data.

60 bytes from 212.58.244.68: icmp_seq=1 ttl=58 time=30.0 ms
--- 212.58.244.68 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rount-trip min/avg/max/mdev = 30.000/30.000/30.000/0.000

7) Use router status screen to see current adsl status

Firmware Version: V1.00.16
MAC Address: 00:1D:7E:B7:DE:C0
Current Time: 14-05-2011 07:41:22
Cisco Logo
Internet Connection

Login Type: RFC 2364 PPPoA
Interface: Up
IP Address: 217.155.xxx.xx
Subnet Mask: 255.255.255.255
Default Gateway: 62.3.84.21
DNS 1: 212.23.6.100
DNS 2: 212.23.3.100
DNS 3:
WINS: ---

Edited by deleted (Sat 14-May-11 09:42:46)

Hi Gary,

From what you've said you don't have a DNS problem, you have a more general Internet connection problem and failure of DNS is a symptom of your disconnections. You should focus more on your line stats, router, and try eliminating problems with the phone wiring and filters by connecting your router directly to the "test socket" behind the faceplate of your BT master socket (assuming you have one). Sounds like you may have a line fault if you can rule out the internal stuff. Someone here or tech support should be able to help you more with this if you need it.

Carl

Indeed - your DNS problem is caused by you getting disconnected from the internet.

Can you post your router line stats etc please.