Intermittent DNS server failure
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Plusnet Community
- :
- Forum
- :
- Help with my Plusnet services
- :
- Broadband
- :
- Intermittent DNS server failure
Intermittent DNS server failure
11-10-2013 7:26 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
From about midday I've been getting intermittent failures of the DNS server to return an address.
Sometimes repeated attempts to load a page (or, better, to ping the site) resolves the problem.
I've rebooted my router two or three times so I don't think it is that and it reports that it has 212.159.6.9 as the primary server and 212.159.6.10 as rhe secondary.
This has happened in the past but has cleared after a time or by rebooting the router.
The sites it has had trouble with are webmail.spamcop.net, duckduckgo.com, and gentoo.org -- is there a problem with DNS to America?
Chris
Re: Intermittent DNS server failure
11-10-2013 7:39 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
http://community.plus.net/forum/index.php/topic,118268.msg1030743.html#msg1030743
Re: Intermittent DNS server failure
11-10-2013 7:44 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
This will eliminate whether you really have a DNS connectivity problem, or whether you have a router problem or wireless issue.
Unfortunately if you are using Windows, it often reports a DNS fault when what has really happened is a general loss of connection.
Re: Intermittent DNS server failure
11-10-2013 7:58 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
@purleigh: thanks -- my router seems to have gone catatonic when asked to change its DNS -- it may be some time before I can post results.
Thank you both for your swift replies
Chris
Re: Intermittent DNS server failure
11-10-2013 8:07 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Re: Intermittent DNS server failure
11-10-2013 8:10 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
You might also want to consider ensuring that you have the latest firmware installed as well.
Re: Intermittent DNS server failure
11-10-2013 9:11 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Here are some answers (thanks to ejs on the other thread for dig)
run-dig.sh 8.8.8.8
; <<>> DiG 9.9.3-P2 <<>> @8.8.8.8 webmail.spamcop.net
;; Query time: 45 msec
;; connection timed out; no servers could be reached
;; Query time: 38 msec
;; Query time: 38 msec
;; Query time: 36 msec
;; Query time: 38 msec
;; Query time: 40 msec
;; Query time: 44 msec
;; Query time: 37 msec
;; Query time: 37 msec
run-dig.sh 208.67.220.220
; <<>> DiG 9.9.3-P2 <<>> @208.67.220.220 webmail.spamcop.net
;; Query time: 41 msec
;; Query time: 31 msec
;; Query time: 31 msec
;; connection timed out; no servers could be reached
;; Query time: 42 msec
;; connection timed out; no servers could be reached
;; Query time: 39 msec
;; Query time: 32 msec
;; connection timed out; no servers could be reached
;; Query time: 40 msec
run-dig.sh 212.159.6.9
; <<>> DiG 9.9.3-P2 <<>> @212.159.6.9 webmail.spamcop.net
;; Query time: 39 msec
;; Query time: 32 msec
;; Query time: 32 msec
;; connection timed out; no servers could be reached
;; Query time: 41 msec
;; Query time: 33 msec
;; Query time: 31 msec
;; Query time: 31 msec
;; Query time: 32 msec
;; Query time: 31 msec
run-dig.sh 212.159.6.10
; <<>> DiG 9.9.3-P2 <<>> @212.159.6.10 webmail.spamcop.net
;; Query time: 39 msec
;; Query time: 30 msec
;; Query time: 33 msec
;; Query time: 33 msec
;; connection timed out; no servers could be reached
;; Query time: 39 msec
;; Query time: 32 msec
;; Query time: 34 msec
;; Query time: 31 msec
;; Query time: 35 msec
Curious, no?
Chris
Re: Intermittent DNS server failure
11-10-2013 10:40 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Quote from: purleigh Google (e.g. - 8.8.8.8).
Time to start inserting a space before the ")", methinks -> 8.8.8.8 )
Using a TP-Link Archer VR600 modem-router.
Re: Intermittent DNS server failure
11-10-2013 11:21 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Re: Intermittent DNS server failure
12-10-2013 8:05 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
But since you also saw failures with Google DNS and OpenDNS, then you probably have a more general problem.
Re: Intermittent DNS server failure
12-10-2013 2:13 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Chris
$ ping 212.159.6.9
PING 212.159.6.9 (212.159.6.9) 56(84) bytes of data.
64 bytes from 212.159.6.9: icmp_seq=1 ttl=250 time=39.4 ms
64 bytes from 212.159.6.9: icmp_seq=2 ttl=250 time=40.8 ms
64 bytes from 212.159.6.9: icmp_seq=3 ttl=250 time=39.2 ms
64 bytes from 212.159.6.9: icmp_seq=4 ttl=250 time=41.6 ms
64 bytes from 212.159.6.9: icmp_seq=5 ttl=250 time=39.6 ms
64 bytes from 212.159.6.9: icmp_seq=6 ttl=250 time=39.3 ms
64 bytes from 212.159.6.9: icmp_seq=7 ttl=250 time=39.7 ms
64 bytes from 212.159.6.9: icmp_seq=8 ttl=250 time=42.1 ms
64 bytes from 212.159.6.9: icmp_seq=9 ttl=250 time=39.0 ms
64 bytes from 212.159.6.9: icmp_seq=10 ttl=250 time=39.5 ms
^C
--- 212.159.6.9 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9013ms
rtt min/avg/max/mdev = 39.014/40.067/42.169/1.079 ms
ping 212.159.6.10
PING 212.159.6.10 (212.159.6.10) 56(84) bytes of data.
64 bytes from 212.159.6.10: icmp_seq=1 ttl=250 time=40.5 ms
64 bytes from 212.159.6.10: icmp_seq=2 ttl=250 time=39.6 ms
64 bytes from 212.159.6.10: icmp_seq=3 ttl=250 time=38.7 ms
64 bytes from 212.159.6.10: icmp_seq=5 ttl=250 time=41.0 ms
64 bytes from 212.159.6.10: icmp_seq=6 ttl=250 time=39.0 ms
64 bytes from 212.159.6.10: icmp_seq=7 ttl=250 time=43.3 ms
64 bytes from 212.159.6.10: icmp_seq=8 ttl=250 time=39.0 ms
64 bytes from 212.159.6.10: icmp_seq=9 ttl=250 time=31.3 ms
64 bytes from 212.159.6.10: icmp_seq=10 ttl=250 time=42.0 ms
64 bytes from 212.159.6.10: icmp_seq=11 ttl=250 time=44.4 ms
^C
--- 212.159.6.10 ping statistics ---
11 packets transmitted, 10 received, 9% packet loss, time 10012ms
rtt min/avg/max/mdev = 31.360/39.929/44.431/3.388 ms
$ ping -c16 212.159.6.9
PING 212.159.6.9 (212.159.6.9) 56(84) bytes of data.
64 bytes from 212.159.6.9: icmp_seq=1 ttl=250 time=42.6 ms
64 bytes from 212.159.6.9: icmp_seq=2 ttl=250 time=40.1 ms
64 bytes from 212.159.6.9: icmp_seq=3 ttl=250 time=42.2 ms
64 bytes from 212.159.6.9: icmp_seq=4 ttl=250 time=39.8 ms
64 bytes from 212.159.6.9: icmp_seq=5 ttl=250 time=39.7 ms
64 bytes from 212.159.6.9: icmp_seq=6 ttl=250 time=31.3 ms
64 bytes from 212.159.6.9: icmp_seq=8 ttl=250 time=39.7 ms
64 bytes from 212.159.6.9: icmp_seq=9 ttl=250 time=39.8 ms
64 bytes from 212.159.6.9: icmp_seq=10 ttl=250 time=43.4 ms
64 bytes from 212.159.6.9: icmp_seq=11 ttl=250 time=40.6 ms
64 bytes from 212.159.6.9: icmp_seq=12 ttl=250 time=40.3 ms
64 bytes from 212.159.6.9: icmp_seq=13 ttl=250 time=39.5 ms
64 bytes from 212.159.6.9: icmp_seq=14 ttl=250 time=40.7 ms
64 bytes from 212.159.6.9: icmp_seq=15 ttl=250 time=40.4 ms
--- 212.159.6.9 ping statistics ---
16 packets transmitted, 14 received, 12% packet loss, time 15021ms
rtt min/avg/max/mdev = 31.307/40.043/43.409/2.687 ms
$ ping -c16 212.159.6.10
PING 212.159.6.10 (212.159.6.10) 56(84) bytes of data.
64 bytes from 212.159.6.10: icmp_seq=1 ttl=250 time=40.7 ms
64 bytes from 212.159.6.10: icmp_seq=2 ttl=250 time=41.6 ms
64 bytes from 212.159.6.10: icmp_seq=3 ttl=250 time=40.0 ms
64 bytes from 212.159.6.10: icmp_seq=4 ttl=250 time=40.0 ms
64 bytes from 212.159.6.10: icmp_seq=5 ttl=250 time=39.5 ms
64 bytes from 212.159.6.10: icmp_seq=6 ttl=250 time=41.5 ms
64 bytes from 212.159.6.10: icmp_seq=7 ttl=250 time=40.0 ms
64 bytes from 212.159.6.10: icmp_seq=8 ttl=250 time=46.7 ms
64 bytes from 212.159.6.10: icmp_seq=9 ttl=250 time=39.7 ms
64 bytes from 212.159.6.10: icmp_seq=10 ttl=250 time=39.9 ms
64 bytes from 212.159.6.10: icmp_seq=11 ttl=250 time=39.9 ms
64 bytes from 212.159.6.10: icmp_seq=12 ttl=250 time=39.4 ms
64 bytes from 212.159.6.10: icmp_seq=13 ttl=250 time=39.5 ms
64 bytes from 212.159.6.10: icmp_seq=15 ttl=250 time=40.6 ms
64 bytes from 212.159.6.10: icmp_seq=16 ttl=250 time=39.5 ms
--- 212.159.6.10 ping statistics ---
16 packets transmitted, 15 received, 6% packet loss, time 15019ms
rtt min/avg/max/mdev = 39.478/40.613/46.721/1.759 ms
Re: Intermittent DNS server failure
12-10-2013 2:35 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Re: Intermittent DNS server failure
12-10-2013 4:52 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Plusnet Community
- :
- Forum
- :
- Help with my Plusnet services
- :
- Broadband
- :
- Intermittent DNS server failure