On 05/11/2020 14:12, Ronald F. Guilmette via db-wg wrote: Hi Ronald,
Can someone (anyone) please explain to me why the following file does not exist?
ftp://ftp.ripe.net/pub/zones/185.in-addr.arpa-RIPE
Who is responsible for generating the files in this directory? What is the process by which they are generated? What went wrong and who is going to fix it?
The files in https://ftp.ripe.net/pub/zones/ are generated by the RIPE NCC's reverse DNS provisioning system. The files published there are "zonelet" files. They are meant to contain reverse DNS delegation information for address space registered in the RIPE Database, but whose parent zone operator is another RIR. For example, 192.in-addr.arpa is operated by ARIN, but there are various address ranges in 192/8 registered in the RIPE Database. So we publish the DNS information in the "192.in-addr.arpa-RIPE" file. ARIN fetches this file periodically to import the data in it into 192.in-addr.arpa. In contrast, 185/8 has been assigned to RIPE NCC by the IANA. So RIPE NCC operates 185.in-addr.arpa. We have no reason to publish a zone file for it on our FTP/HTTPS server. You can query this zone's name servers directly if you want to see delegation information. There is nothing wrong, and nothing to fix.
And more to the point, where may I find the real, actual, and complete set of zone files? Are they hidden away behind some curtain, or in some secret room? Who do I have to know in order to be invited to view the real zonefiles that are actually being used for delegation?
dig 185.in-addr.arpa axfr @pri.authdns.ripe.net > 185.in-addr.arpa.zone Regards, Anand Buddhdev RIPE NCC