Intermittent resolution issues
191 views
Skip to first unread message
Nicholas Bayle
Oct 24, 2013, 11:23:08 PM10/24/13
to public-dn...@googlegroups.com
Hello-
We've been using the Google public dns servers as upstream servers for our local maradns installation for several years and it's all worked very well. Within the last week or so, we've seen lots of requests that are very slow to resolve or never resolve at all. I realize this could possibly be something with maradns, though no configuration change has been made.
These commands are from the gateway machine that also runs maradns. Keep in mind that the internet connection is always up during these issues and the addresses can be resolved when using another DNS server.
$ askmara Agoogle.com.
# Querying the server with the IP 127.0.0.1
# Remote server said: SERVER FAILURE
# Question: Agoogle.com.
# NS replies:
# AR replies:
$ askmara Agoogle.com.
# Querying the server with the IP 127.0.0.1
# Remote server said: FORMAT ERROR
# Question: Agoogle.com.
# NS replies:
# AR replies:
$ askmara Agoogle.com.
# Querying the server with the IP 127.0.0.1
^C
$ askmara Agoogle.com.
# Querying the server with the IP 127.0.0.1
# Question: Agoogle.com.
google.com. +251 a 74.125.225.137
google.com. +251 a 74.125.225.134
google.com. +251 a 74.125.225.132
google.com. +251 a 74.125.225.131
google.com. +251 a 74.125.225.129
google.com. +251 a 74.125.225.142
google.com. +251 a 74.125.225.135
google.com. +251 a 74.125.225.130
# NS replies:
# AR replies:
$
Then, using dig:
$ dig @8.8.8.8 google.com.
; <<>> DiG 9.4.2-P2 <<>> @8.8.8.8 google.com.
; (1 server found)
;; global options: printcmd
;; connection timed out; no servers could be reached
$ dig @8.8.4.4 google.com.
; <<>> DiG 9.4.2-P2 <<>> @8.8.4.4 google.com.
; (1 server found)
;; global options: printcmd
;; connection timed out; no servers could be reached
Note that with another DNS server, it resolves OK:
$ dig @75.75.75.75 google.com.
; <<>> DiG 9.4.2-P2 <<>> @75.75.75.75 google.com.
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50508
;; flags: qr rd ra; QUERY: 1, ANSWER: 11, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;google.com. IN A
;; ANSWER SECTION:
google.com. 106 IN A 173.194.33.128
google.com. 106 IN A 173.194.33.133
google.com. 106 IN A 173.194.33.130
google.com. 106 IN A 173.194.33.131
google.com. 106 IN A 173.194.33.136
google.com. 106 IN A 173.194.33.129
google.com. 106 IN A 173.194.33.134
google.com. 106 IN A 173.194.33.132
google.com. 106 IN A 173.194.33.142
google.com. 106 IN A 173.194.33.135
google.com. 106 IN A 173.194.33.137
;; Query time: 16 msec
;; SERVER: 75.75.75.75#53(75.75.75.75)
;; WHEN: Thu Oct 24 19:43:48 2013
;; MSG SIZE rcvd: 204
Ping and a traceroute:
$ ping google.com
PING google.com (173.194.33.65): 56 data bytes
64 bytes from 173.194.33.65: icmp_seq=0 ttl=57 time=4.925 ms
--- google.com ping statistics ---
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 4.925/4.925/4.925/0.000 ms
$ sudo traceroute -n -w 2 -q 2 -m 30 8.8.8.8
Password:
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 40 byte packets
1 50.200.192.49 0.510 ms 0.415 ms
2 68.86.99.149 45.926 ms 4.291 ms
3 68.86.93.165 8.507 ms 68.86.95.249 6.733 ms
4 68.86.84.78 5.35 ms 5.36 ms
5 * 75.149.231.90 49.166 ms
6 209.85.249.32 4.866 ms 4.842 ms
7 66.249.94.197 5.46 ms 66.249.94.199 5.50 ms
8 216.239.46.200 11.967 ms 216.239.46.208 12.157 ms
9 216.239.48.167 12.414 ms 11.923 ms
10 * *
11 8.8.8.8 12.30 ms 11.997 ms
Suddenly, it comes back to life, but dies a few minutes later:
$ dig @8.8.8.8 google.com.
; <<>> DiG 9.4.2-P2 <<>> @8.8.8.8 google.com.
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39103
;; flags: qr rd ra; QUERY: 1, ANSWER: 11, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;google.com. IN A
;; ANSWER SECTION:
google.com. 184 IN A 74.125.225.136
google.com. 184 IN A 74.125.225.128
google.com. 184 IN A 74.125.225.142
google.com. 184 IN A 74.125.225.135
google.com. 184 IN A 74.125.225.137
google.com. 184 IN A 74.125.225.134
google.com. 184 IN A 74.125.225.131
google.com. 184 IN A 74.125.225.132
google.com. 184 IN A 74.125.225.129
google.com. 184 IN A 74.125.225.133
google.com. 184 IN A 74.125.225.130
;; Query time: 27 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Thu Oct 24 19:45:07 2013
;; MSG SIZE rcvd: 204
$ dig @8.8.8.8 google.com.
; <<>> DiG 9.4.2-P2 <<>> @8.8.8.8 google.com.
; (1 server found)
;; global options: printcmd
;; connection timed out; no servers could be reached
Does anyone have any clue what is going on here?
Thanks!
Nick
Yunhong Gu
Oct 24, 2013, 11:37:52 PM10/24/13
to public-dn...@googlegroups.com
If you cannot resolve any query during that certain outage period, maybe it was because your local DNS server was sending too many queries to us (we have a 100QPS limit by default). If this does not explain what happened, please create a ticket at https://code.google.com/a/google.com/p/public-dns/issues/list.
--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to
public-dns-disc...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-disc...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Reply all
Reply to author
Forward
0 new messages