Skip to Content.
Sympa Menu

dns-operations - Re: [opennic-dns-operations ] T2 Operators: dotPirate Has Been Approved

dns-operations AT lists.opennicproject.org

Subject: Dns-operations mailing list

List archive

Re: [opennic-dns-operations ] T2 Operators: dotPirate Has Been Approved


Chronological Thread 
  • From: Jeff Taylor <shdwdrgn AT sourpuss.net>
  • To: dns-operations AT lists.opennicproject.org
  • Subject: Re: [opennic-dns-operations ] T2 Operators: dotPirate Has Been Approved
  • Date: Wed, 16 May 2012 07:02:44 -0600

If you look at the current root zone (2012051603) you will see that NS4
and NS6 are *not* listed for the pirate zone, and NS4 is not listed for
the neo zone. This is one of the functions of the hourly rebuild of the
root zone -- to de-list any T1 servers which are not currently resolving
each zone.

The tier-2 servers which randomly fail to resolve the new zones are most
likely passing all of their queries off to a short list of T1 servers.
If those admins do not stay on top of updating their masters list to
match the current functioning servers, then there can be issues like we
are seeing now.


On 05/16/2012 04:58 AM, Bryon Eldridge wrote:
>> Correct... NS4 and NS6 have still not added the pirate zone. Also we're
>> still waiting on NS4 to add the neo zone. The T2 servers that are failing
>> these zones are due to their configuration - passing the queries directly
>> to
>> the T1 servers, which of course will do round-robin and occasionally hit
>> one
>> of the T1s that do not have the records.
> I would argue that it's because the . zone is pointing to invalid
> servers. I think that the T1 servers shouldn't be added to the . zone
> unless they're working. We take T2 servers out of the
> dns.opennic.glue zone when they're not working, so why not the same
> for T1s?



Archive powered by MHonArc 2.6.19.

Top of Page