19 Jul
2019
19 Jul
'19
2:52 p.m.
On Fri, Jul 19, 2019 at 11:54:55AM -0700, Cory (NQ1E) wrote:
Indeed, rdns for HamWAN is still broken
(44.25.0.0/16). It appears to be
because second level delegations were made on ARIN's DNS servers for every
"44.x" label. Since that's at the same level as our delegation, DNS
servers see it as an invalid "horizontal" delegation.
same here,
$ i=0; while [ $i -lt 256 ]; do host 44.$i.0.0 ; i=$(($i+1)); done|grep SERVF
Host 0.0.25.44.in-addr.arpa not found: 2(SERVFAIL)
Host 0.0.130.44.in-addr.arpa not found: 2(SERVFAIL)
Host 0.0.140.44.in-addr.arpa not found: 2(SERVFAIL)
Host 0.0.148.44.in-addr.arpa not found: 2(SERVFAIL)
Host 0.0.149.44.in-addr.arpa not found: 2(SERVFAIL)
(and:
Host 0.0.224.44.in-addr.arpa not found: 2(SERVFAIL)
Host 0.0.225.44.in-addr.arpa not found: 2(SERVFAIL)
..forget about them)
140.44.in-addr.arpa is Sweden.
$ dig 60.100.130.44.in-addr.arpa ptr +trace
...
130.44.in-addr.arpa. 3600 IN NS db0fhn.efi.fh-nuernberg.de.
130.44.in-addr.arpa. 3600 IN NS db0res.de.
130.44.in-addr.arpa. 3600 IN NS ns.db0fhn.ampr.org.
;; BAD (HORIZONTAL) REFERRAL
dig: too many lookups
=> 44.0.0.1 delegaes NS for 44.25, 44.130, 44.140, 44.148, 44.149 and that
got broken.
No glue issue (see db0res.de, or ns.ssvl.kth.se).
Perhaps due to the fact that primary and secondary nameservers are configured
to serve 44.in-addr.arpa, but in-addr.arpa has a smaller scope.
vy 73,
- Thomas dl9sau