While I think FreeBSD generally should try to push the "state of the art" envelope, it seems to me that this change may be premature, in particular if the people providing the AXFR-service on which it depends, are not prepared to officially offer the service. So for this change to remain in FreeBSD, one of two things will have to happen: A) At least three (A number found on my paint-bucket) root servers must sign up to provide the public AXFR for at least 3 (ditto) years. or B) FreeBSD systems so configured, shall keep working flawlessly if the AXFR service becomes unavailable. What should not under any circumstances happen: C) The unannounced service is terminated and all so configured FreeBSD systems wedge. That said, I fully agree with the spirit of this change, I have myself seen what positive difference it makes for servers in Denmark to have a slave of the .dk zone, particular for busy mailservers. I hope we can swing for solution A) Poul-Henning -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk_at_FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.Received on Thu Aug 02 2007 - 03:59:50 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:15 UTC