-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
Relevant to another post today, I've noticed that neither the *.ip6-servers.arpa nor the *.in-addr-servers.arpa allow axfr. Which leads to the following questions:
1. Was that a conscious decision, and if so why? Speaking for the operator of f.in-addr-servers.arpa and f.ip6-servers.arpa this was simply not on our radar.
2. Is there any hope that axfr could be permitted in the future? Since we are also operating k.root-servers.net and have provided XFR from it for all this time we will do so for these servers as well. This has now been enabled on our systems.
Regards, Wolfgang Nagele RIPE NCC DNS Group Manager -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1dOrcACgkQjO7G63Byy8f5hACgmRBBPCYlPI4vVumvAwyWZAgJ t8MAoJs4BOwzKiKYwNjYY9oOIADlhTzs =aFMj -----END PGP SIGNATURE-----