[dns-operations] problems with 107.54.66.in-addr.arpa

[Mark Andrews]

In message <AANLkTim75K7ddLBvsHdwi=MZhsjOPM7VVQS17hHWFi1t at mail.gmail.com>, "Pau
l S. R. Chisholm" writes:
> Summary: 107.54.66.in-addr.arpa is delegated to two nameservers. One
> delegates to a nameserver that doesn't respond, the other lamely
> delegates.
> 
> All the roots report that 107.54.66.in-addr.arpa is delegated to
> {t...z}.arin.net and dill.arin.net, and all of them report it's
> delegated to ns1.forona.net and ns2.forona.net:
> 
> $ for i in {t..z}.arin.net dill.arin.net; do echo $i:::;  dig +nocmd
> +noquestion +nostats +norecurse @$i 94.107.54.66.in-addr.arpa. ptr;
> done
> t.arin.net:::
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60100
> ;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 0
> 
> ;; AUTHORITY SECTION:
> 107.54.66.in-addr.arpa.	86400	IN	NS	ns2.forona.net.
> 107.54.66.in-addr.arpa.	86400	IN	NS	ns1.forona.net.
> 
> [and similarly for the other arin.net servers]
> 
> $ for i in ns{1..2}.forona.net; do host $i; done
> ns1.forona.net has address 67.159.206.12
> ns2.forona.net has address 67.159.206.22
> 
> Of these, one (ns1.forona.net) further delegates:
> 
> $ dig +nocmd +noquestion +nostats +norecurse @67.159.206.12
> 94.107.54.66.in-addr.arpa. ptr
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21187
> ;; flags: qr ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
> 
> ;; AUTHORITY SECTION:
> 94.107.54.66.in-addr.arpa. 4200	IN	NS	ddsns1.central-dns.net.
> 
> ;; ADDITIONAL SECTION:
> ddsns1.central-dns.net.	596	IN	A	67.159.206.2
> 
> $ host ddsns1.central-dns.net.  # Is the glue correct? Yes:
> ddsns1.central-dns.net has address 67.159.206.2
> 
> ... but the nameserver it delegates to is not responding:
> 
> $ dig +nocmd +noquestion +nostats +norecurse @67.159.206.2
> 94.107.54.66.in-addr.arpa. ptr
> ;; connection timed out; no servers could be reached
> 
> The other (ns2.forona.net) delegates lamely:

More correctly it is lame for 107.54.66.in-addr.arpa.
 
> $ dig +nocmd +noquestion +nostats +norecurse @67.159.206.22
> 94.107.54.66.in-addr.arpa. ptr
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 42010
> ;; flags: qr ra; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 0
> 
> ;; AUTHORITY SECTION:
> 107.54.66.in-addr.arpa.	84960	IN	NS	ns1.forona.net.
> 107.54.66.in-addr.arpa.	84960	IN	NS	ns2.forona.net.
> 
> Hope this helps.  --PSRC
> 
> P.S.: Feedback welcome on how or where to better report this kind of problem

You can always do a whois lookup and report through the contacts there.

whois -h whois.arin.net NET-66-54-96-0-1
and whois -h whois.arin.net NET-66-54-107-64-1

> _______________________________________________
> dns-operations mailing list
> dns-operations at lists.dns-oarc.net
> https://lists.dns-oarc.net/mailman/listinfo/dns-operations
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka at isc.org