Dns-operations mailing list

[Jeff Taylor <shdwdrgn AT sourpuss.net>]

This is all pretty typical.  Under normal operations, a zone will only
update within it's TTL, which can be hours or days.  Zones like free and
geek get updated quite frequently, so its not unusual for the other
servers to be out of sync.  And for all you know, a fresh zone may have
been sent out just minutes before the report was generated.

What does stick out to me as unusual is that I am not seeing any
notifies for the gopher zone from NS7, and that zone is two days out of
date on a number of servers.  I would hope that all of the T1
administrators have notify enabled for ALL of the TLD zones, but
especially for and zone they are the master for.

NS4 actually picked up the oz zone about 7 hours ago, but we're still
waiting on NS6.  This issue has been reflected on the t2log page. 
Pretty much anything that is an actual problem with the servers would be
shown there.  The reports sent to the mailing list will show the details
of what is discovered about each server, but those details do not
necessarily indicate a problem.


On 06/24/2012 01:57 AM, Amrit Panesar wrote:
> some problems here:
>
> ns21 seems to have an axfr transferring issue.
> ns3 and ns21 seem to be out of sync on .free
> everyone is out of sync on .geek
> half of the listed nameservers for gopher are out of sync
> ns3 is out of sync on .indy
> everyone is out of sync on .null
> ns4 and ns6 do not have .oz
> ns8 is out of sync on .oz