19 Jul
2019
19 Jul
'19
1:54 p.m.
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.
Can you please see that the "25.44.in-addr.arpa." record is updated in
ARIN's DNS servers to point to:
a.ns.hamwan.net.
b.ns.hamwan.net.
Thank you,
-Cory, NQ1E
HamWAN
$ dig +trace 25.44.in-addr.arpa.
<snip>
44.in-addr.arpa. 86400 IN NS z.arin.net.
44.in-addr.arpa. 86400 IN NS x.arin.net.
44.in-addr.arpa. 86400 IN NS r.arin.net.
;; Received 92 bytes from 200.10.60.53#53(200.10.60.53) in 232 ms
25.44.in-addr.arpa. 86400 IN NS ns2.threshinc.com.
25.44.in-addr.arpa. 86400 IN NS ampr-dns.in-berlin.de.
25.44.in-addr.arpa. 86400 IN NS a.coreservers.uk.
25.44.in-addr.arpa. 86400 IN NS ampr.org.
25.44.in-addr.arpa. 86400 IN NS munnari.oz.au.
;; Received 181 bytes from 199.180.180.63#53(199.180.180.63) in 498 ms
25.44.in-addr.arpa. 3600 IN NS a.ns.hamwan.net.
25.44.in-addr.arpa. 3600 IN NS c.ns.hamwan.net.
25.44.in-addr.arpa. 3600 IN NS b.ns.hamwan.net.
;; BAD (HORIZONTAL) REFERRAL
;; Received 97 bytes from 192.109.42.4#53(192.109.42.4) in 269 ms
25.44.in-addr.arpa. 3600 IN SOA a.ns.hamwan.net.
hostmaster.hamwan.net. 2019071706 900 180 604800 900
;; Received 98 bytes from 44.24.245.2#53(44.24.245.2) in 11 ms
On Fri, Jul 19, 2019 at 7:40 AM Tom Hayward via 44Net <
44net(a)mailman.ampr.org> wrote:
---------- Forwarded message ----------
From: Tom Hayward <esarfl(a)gmail.com>
To: AMPRNet working group <44net(a)mailman.ampr.org>
Cc:
Bcc:
Date: Fri, 19 Jul 2019 07:38:57 -0700
Subject: Re: [44net] Reverse DNS broken
Seems 44.25.0.0/16 is still broken. It was previously delegated to [abc].
ns.hamwan.net.
Tom KD7LXL
On Fri, Jul 19, 2019, 05:07 Job Snijders <job(a)ntt.net> wrote:
should
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
---------- Forwarded message ----------
From: Tom Hayward via 44Net <44net(a)mailman.ampr.org>
To: AMPRNet working group <44net(a)mailman.ampr.org>
Cc: Tom Hayward <esarfl(a)gmail.com>
Bcc:
Date: Fri, 19 Jul 2019 07:38:57 -0700
Subject: Re: [44net] Reverse DNS broken
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
I think this is resolved now.
On Fri, Jul 19, 2019 at 02:37 Job Snijders <job(a)ntt.net> wrote:
> Some good debugging information was provided to me offlist , I've now
> been in touch with ARIN staff and some changes were made. It may take a
> few hours for the changes to be visible on the Internet, new zone file
> needs to be generated & pushed out.
>
> My initial assessment is that the delegations for the remaining /10 and
> /9 towards AMPRnet DNS servers didnt exist. I don't know whose
> responsiblity it would've been to ensure that existed. I can't guess
why
> they were missing, perhaps a coordination
issue in the transfer process
> from the previous state to the current state.
>
> The AMPRnet reverse DNS administators may want to verify that the
> authoritative dns servers are configured not for for 44.in-addr.arpa,
> but for the individual /16s within 44/8 that still are AMPRnet. I don't
> know who manages that so I hope this message finds them.
>
> I'm running on fumes and only have 4 hours of sleep opportunity ahead
of
me - so
signing off, I think things will probably restore in the next
few hours.
Good luck!
Job
On Fri, Jul 19, 2019 at 05:27:27AM +0000, Job Snijders wrote:
> To help speed up the resolution process, it would be beneficial if
> someone provides me with data what exactly is broken, and what the
> values / parameters previously were.
>
> was 44.in-addr.arpa. previously delegated to z.arin.net, x.arin.net,
and
> > r.arin.net? If not, where was it delegated? Where should it be
> > delegated?
> >
> > Any tangible data about what the state currently is, and what it be; will help speed up recovery.
Kind regards,
Job