Re: [public-dns-discuss] Google DNS not resolving some domains

232 views
Skip to first unread message
Message has been deleted

Yunhong Gu

unread,
Jan 24, 2013, 11:57:04 AM1/24/13
to public-dn...@googlegroups.com
There are some issues for the name servers: http://www.intodns.com/ip-monitor.com.ar


On Thu, Jan 24, 2013 at 12:16 AM, <pupi...@gmail.com> wrote:
Hi,

It's been a couple of months since I haven't been able to resolve some domains using Google DNS. I've been able to resolve them using other DNS servers, though.

Here are some outputs of commands that might help. Let me know if you need anything else to help me solve this issue. Thanks in advance.

$ sudo traceroute -n -w 2 -q 2 -m 30 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  192.168.0.1  7.031 ms  7.014 ms
 2  * *
 3  * *
 4  * *
 5  * *
 6  200.89.165.185  116.061 ms 200.89.165.181  115.806 ms
 7  200.89.165.130  115.677 ms  115.627 ms
 8  200.89.165.222  115.764 ms  115.650 ms
 9  * *
10  209.85.251.86  205.493 ms 209.85.251.84  205.324 ms
11  209.85.252.42  209.324 ms  209.359 ms
12  72.14.233.89  205.313 ms 72.14.233.93  205.322 ms
13  64.233.175.18  205.850 ms  205.728 ms
14  8.8.8.8  203.604 ms  203.649 ms



; <<>> DiG 9.7.3 <<>> @8.8.8.8 www.ip-monitor.com.ar
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 59239
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:

;; Query time: 1693 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Thu Jan 24 02:10:35 2013
;; MSG SIZE  rcvd: 39


$ nslookup www.ip-monitor.com.ar 4.2.2.1
Server: 4.2.2.1
Address: 4.2.2.1#53

Non-authoritative answer:
Address: 67.220.217.235


$ nslookup www.ip-monitor.com.ar 4.2.2.2
Server: 4.2.2.2
Address: 4.2.2.2#53

Non-authoritative answer:
Address: 67.220.217.235


$ nslookup www.ip-monitor.com.ar 208.67.222.222
Server: 208.67.222.222
Address: 208.67.222.222#53

Non-authoritative answer:
Address: 67.220.217.235


$ nslookup www.ip-monitor.com.ar 208.67.220.220
Server: 208.67.220.220
Address: 208.67.220.220#53

Non-authoritative answer:
Address: 67.220.217.235

--
--
========================================================
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
========================================================
 
 
 

Message has been deleted

Jeremy K. Chen (陳康本)

unread,
Feb 15, 2013, 2:44:37 PM2/15/13
to public-dn...@googlegroups.com
Hi,

An authoritative server 199.19.56.1 for the .org zone tells us that ns1.zzl.org and ns2.zzl.org are authoritative for zzl.org and gives us glue addresses 67.220.217.226 and 67.220.217.229.  

; <<>> DiG 9.8.1-P1 <<>> ns1.zzl.org @199.19.56.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8800
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 2
;; WARNING: recursion requested but not available

;; QUESTION SECTION:

;; AUTHORITY SECTION:
zzl.org. 86400 IN NS ns1.zzl.org.
zzl.org. 86400 IN NS ns2.zzl.org.

;; ADDITIONAL SECTION:
ns1.zzl.org. 86400 IN A 67.220.217.226
ns2.zzl.org. 86400 IN A 67.220.217.229


But the problem is, when you query 67.220.217.226 about ns2.zzl.org, you get a different answer 67.220.217.235:

; <<>> DiG 9.8.1-P1 <<>> ns2.zzl.org @67.220.217.226
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49549
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:

;; ANSWER SECTION:
ns2.zzl.org. 86400 IN A 67.220.217.235


RFC considers that the address in the "ANSWER SECTION" is more authoritative than the address in "ADDITIONAL SECTION" above. But if you use 67.220.217.235 to query www.ip-monitor.com.ar, you get nothing:

; <<>> DiG 9.8.1-P1 <<>> @67.220.217.235 www.ip-monitor.com.ar
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached


Also, if you query 67.220.217.226 about ns1.zzl.org, you get NXDOMAIN, which means that "this domain doesn't exist".  This is wrong:
; <<>> DiG 9.8.1-P1 <<>> ns1.zzl.org @67.220.217.226
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 23099
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:

;; AUTHORITY SECTION:
zzl.org. 86400 IN SOA ns1.zzl.org. ns2.zzl.org. 1 10800 3600 604800 3600

I suggest that you contact your Registar who is responsible for running the zzl.org zone to fix the nameserver records.



On Fri, Feb 15, 2013 at 11:21 AM, <pupi...@gmail.com> wrote:
Hi Yunhong,

Sorry, to get this into life again. But I checked with zzl.org guys and they say the issue is in the registrar. I still have doubts about this. Whatsmore, ns1.zzl.org seems to be down right now. The thing that concerns me the most is why I can resolve this host using my ISP dns and not yours, which of course, I trust more. Could you help me understand that? I've been seeing this behaviour for months... but has not always been this way.

Additionally, is there any way I can tell if the issue is in zzl.org or in my registrar?

Any clue to a newbie like me will be helpful. Thanks!

PS: A similar complain was reported for this site www.silverbay-marina.com (I can't access it with google dns either but I can with my ISP dns servers)

Thanks!

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 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.
 
 



--

Jeremy Chen | Software Engineer |  jerem...@google.com 
 
Reply all
Reply to author
Forward
0 new messages