On Jun 25, 2008, at 3:20 PM, Dean Anderson wrote:
So why deny AXFR from roots, then?
AXFR constitutes a significantly greater load on a name server than
simply answering normal queries. As such, independent root server
operators may decide to restrict zone transfer from their root
On 25 Jun 2008, at 18:20, Dean Anderson wrote:
So why deny AXFR from roots, then?
I'll note that this is a matter for individual root operators, so the
question is better directed at them, individually. However, as a
trivial refutation of the implication that all root servers deny AXFR,
On Wed, 25 Jun 2008, David Conrad wrote:
On Jun 25, 2008, at 3:20 PM, Dean Anderson wrote:
So why deny AXFR from roots, then?
AXFR constitutes a significantly greater load on a name server than
simply answering normal queries. As such, independent root server
operators may decide to
On Jun 25, 2008, at 4:19 PM, Dean Anderson wrote:
BTW, can you explain what these zones are?
http://idn.icann.org/#The_example.test_names
Regards,
-drc
___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
Dean Anderson wrote:
BTW, can you explain what these zones are?
XN--KGBECHTV. NS A.IANA-SERVERS.NET
Wow, an interesting, operationally pertinent question. It deserves mild
praise and an answer.
See http://www.iana.org/reports/2007/testetal-report-01aug2007.html
(Things that start with
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
