Google public IPv6 reverse DNS issue

340 views
Skip to first unread message

jeam...@gmail.com

unread,
Feb 9, 2017, 10:12:18 AM2/9/17
to public-dns-discuss

It appears that Google IPv6 DNS servers don’t respond to a reverse DNS request for the servers.
The IPv4 servers do respond
Note the first lookup is to one of my local DNS servers
Lookups from my Windows 10 laptop


gdns.txt

Alex Dupuy

unread,
Feb 9, 2017, 1:51:30 PM2/9/17
to public-dns-discuss, jeam...@gmail.com
The second argument to nslookup (whether IP address or DNS resolver hostname) is always resolved using the system default resolver (whatever that is).

The errors:

DNS request timed out.
    timeout was 2 seconds.
Server:  UnKnown
Address:  2001:4860:4860::8888

are caused by Windows nslookup trying to reverse-resolve the IPv6 address to a name (Unix/Linux nslookup doesn't bother with that any more, it just prints the IP address for Server and Address). There may have been some temporary issue with reverse delegation in ip6.arpa, but whatever that was, I'm not seeing it besides a few places here and there (and inside China, whose Great Firewall seems to mangle or drop responses some times): https://www.nslookuptool.com/#PTR/2001:4860:4860::8888


jeam...@gmail.com

unread,
Feb 9, 2017, 4:31:21 PM2/9/17
to public-dns-discuss, jeam...@gmail.com



Thanks for the response
It does appear to be a temporary issue.
Today ::8888 is responding to the reverse lookup but  ::8844 still times out.

My default resolvers are my local caching servers running Bind9 under Arch Linux.
Their first forwarder is 2001:470:20::2 (Hurricane Electric).
My Public IPv6 addresses are 2001:470:xxxx::/48 from the Hurricane Electric Dallas 6in4 server
I stumbled across this testing my new reverse zone for “fdxx”


Reply all
Reply to author
Forward
0 new messages