On Fri, Mar 11, 2005 at 07:37:56PM -0500, Kevin Darcy wrote:
> No, that's not a BIND bug. You've left the old version of the zone 
> running on ns1.pbi.net and ns2.pbi.net, and they'll keep on giving out 
> the stale NS records in response to queries. Other caching nameservers 
> such as aludra.usc.edu which had the NS records cached from prior to the 
> switchover will keep on using those nameservers to resolve nakos.net 
> names, and therefore keep seeing regurgitations of the stale NS records, 
> and the cycle will repeat until those caching nameservers are restarted 
> or those particular records in their caches expire or are purged out, or 
> until the pbi.net nameservers stop answering with stale NS records for 
> the zone (i.e. the zone is removed from them or is replaced by a more 
> up-to-date version).
Also, every other DNS server I can find on the net has up-to-date information
- it's only our USC servers that have the old info... which makes me very
  suspicious that no server "should" legitimately pick this up until the old
NS servers go away. As I said, the stale record in question here comes from
the root servers (well, the .net servers), not ns1.pbi.net...

-- 
Phil Dibowitz
Systems Architect and Administrator
Enterprise Infrastructure / ISD / USC
UCC 174 - 213-821-5427


-- Attached file included as plaintext by Ecartis --

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFCNLfS7lkZ1Iyv898RAmuhAJ0anI+I83v9RtA/ZZYYKOyJCmEaMQCfQbLM
/XLFso9lqJjhrsHDHNSFsb4=
=sOiy
-----END PGP SIGNATURE-----