[dns-operations] 127.in-addr.arpa zone
jabley at hopcount.ca
Thu Aug 25 15:46:04 UTC 2011
On 2011-08-21, at 11:05, Mike Jones wrote:
> I doubt it causes any operational issues anywhere with this specific
> zone, but I was testing a diagnostic tool i was working on and did a
> PTR lookup on 188.8.131.52.in-addr.arpa and noticed the following:
> a.in-addr-servers.arpa. is serving 0.0.127.in-addr.arpa. with a PTR
> record for 184.108.40.206.in-addr.arpa. resolving as "localhost"
> d.in-addr-servers.arpa. is serving 0.0.127.in-addr.arpa. with NXDOMAIN
> for 220.127.116.11.in-addr.arpa.
> e.in-addr-servers.arpa. is serving 0.0.127.in-addr.arpa. with a PTR
> record for 18.104.22.168.in-addr.arpa. resolving as "localhost" on IPv6,
> and NXDOMAIN under in-addr.arpa. on IPv4 (hu?)
> the other in-addr servers are all returning NXDOMAIN under the
> in-addr.arpa. zone
From my little corner of the Internet, it looks like all of *.IN-ADDR-SERVERS.ARPA and *.IP6-SERVERS.ARPA are now generating appropriate responses for the v4 and v6 localhost (QNAME, QTYPE)s you mentioned. Thanks for the heads-up.
More information about the dns-operations