Unable to resolve a .com domain via google DNS (timeout) that resolves elsewhere

[Kevin Gadd]

Earlier today I was sent a link to a website and discovered I could
not resolve it using google DNS. Here's the result from resolving it
via zoneedit's website:

derekyu.com
derekyu.com. 360 IN A 69.175.81.15
A derekyu.com

If I nslookup the domain myself, the requests for the domain to the
google DNS server time out. The requests for the domain with my
network suffix properly return nxdomain and I've tested doing nslookup
against other random websites and Google DNS seems to return a valid
result promptly.

Here's the output from another DNS lookup source that is more
detailed:
Searching for derekyu.com. A record at I.ROOT-SERVERS.NET.
[192.36.148.17] ...took 3 ms
Searching for derekyu.com. A record at b.gtld-servers.net.
[192.33.14.30] ...took 28 ms
Searching for ns1.m02.siteground.biz. A record at D.ROOT-SERVERS.NET.
[128.8.10.90] ...took 102 ms
Searching for ns1.m02.siteground.biz. A record at e.gtld.biz.
[156.154.126.65] ...took 128 ms
Searching for NS2.SGDED.COM. A record at F.ROOT-SERVERS.NET.
[192.5.5.241] ...took 17 ms
Searching for NS2.SGDED.COM. A record at h.gtld-servers.net.
[192.54.112.30] ...took 19 ms
Searching for NS2.SGDED.COM. A record at ns1.sgvps.net.
[70.84.112.90] ...took 123 ms
Searching for ns1.m02.siteground.biz. A record at NS2.SGDED.COM.
[67.15.250.250] ...took 119 ms
Searching for derekyu.com. A record at ns1.m02.siteground.biz.
[69.175.48.138] ...took 121 ms

A record found: 69.175.81.15
Domain Type TTL Answer
derekyu.com. NS 86400 ns2.m02.siteground.biz.
derekyu.com. NS 86400 ns1.m02.siteground.biz.
derekyu.com. A 360 69.175.81.15

I set nslookup to full debug mode locally but unfortunately the only
information it gave me for this failed request is that it 'timed out'.

[Jeremy K. Chen (陳康本)]

Hi Kevin,

Thanks for reporting this issue to us, and I am sorry for the problem
that you experienced.

The two nameservers (69.175.48.138 and 69.175.48.139) that are
authoritative for derekyu.com are blocking our IP addresses in certain
regions (mainly on US West Coast). We are in contact with the
administrator to unblock us.

Thanks

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

--
Jeremy K. Chen, Ph.D.
Google New York Software Engineer

[Jeremy K. Chen (陳康本)]

Hi,

In the past few days, we have been working with SingleHop, who was
responsible for these two nameservers, on this issue. The problem has
been resolved. Please check again.

Thanks

[Kevin Gadd]

Working perfectly, thank you.

-kg

On Fri, Dec 17, 2010 at 8:57 AM, Jeremy K. Chen (陳康本)