Re: [44net] Reverse DNS broken

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,