🚀 go-pugleaf

In article <sean.694545284@coombs>, sean@coombs.anu.edu.au (Sean Batt) writes:
|> I just tried to ftp to ftp.uu.net (to have a look at the BSD
|> networking sorces) and got this:
|> 
|> 	coombs:~/ [153] ftp ftp.uu.net
|> 	Connected to uunet.UU.NET.
|> 	530- UUNET's archives are on ftp.uu.net, not uunet.uu.net.  Please
|> 	530- retry using the proper hostname.  The old cname for ftp.uu.net
|> 	530- should have timed out from all nameservers.
|> 	530 Access denied.
|> 
|> How can I find out if this is this a local ANU problem, a national
|> problem or an international problem? I need to know which God to pray
|> to :-)

The patron saint of the DNS (which, judging by the way bind works is falling
down badly on some aspects of the job).

The old CNAME is taking some time to be flushed from the various DNS caches.
I did try flushing the cache on uneeda.aarnet.edu.au (the forwarder for
many au sites) and immediately uneeda relearned the offending CNAME record.

Generally the way you can diagnose this is to use the DIG utility and
see where your information is coming from. Of course it is a bit of an
exercise in frustration to come up with an answer that you can see
that something is broken, but can't do an awful lot about it!

So the answer is to wait (and wait and wait and wait in some cases)
until the bogus stale information is flushed out around the world. Of
course you could always embark on a massive rewrite of bind while you
are waiting  :-)


Geoff Huston
AARNet