On Wed, Jun 25, 2008 at 7:06 PM, Joe Abley <[EMAIL PROTECTED]> wrote:
> a.root-servers.net does not leave AXFR wide open, at least for this client > b.root-servers.net does leave AXFR wide open, at least for this client > c.root-servers.net does leave AXFR wide open, at least for this client > d.root-servers.net does not leave AXFR wide open, at least for this client > e.root-servers.net does not leave AXFR wide open, at least for this client > f.root-servers.net does leave AXFR wide open, at least for this client > g.root-servers.net does leave AXFR wide open, at least for this client > h.root-servers.net does not leave AXFR wide open, at least for this client > i.root-servers.net does not leave AXFR wide open, at least for this client > j.root-servers.net does not leave AXFR wide open, at least for this client > k.root-servers.net does leave AXFR wide open, at least for this client > l.root-servers.net does not leave AXFR wide open, at least for this client > m.root-servers.net does not leave AXFR wide open, at least for this client > Thats not bad. I remember a time when only the f root would AXFR. 5 out of 13 is not bad. -- Joe Baptista www.publicroot.org PublicRoot Consortium ---------------------------------------------------------------- The future of the Internet is Open, Transparent, Inclusive, Representative & Accountable to the Internet community @large. ---------------------------------------------------------------- Office: +1 (360) 526-6077 (extension 052) Fax: +1 (509) 479-0084
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
