The following received during the night:
Quote:
|
Actually we don't see any traces of ns1/ns2.dnsrouter.com left in the zone files. What is possible is that the DNS zones are cached where you're running them through, in which case it depends on when their cache expires (usually within a few hours).
|
The good sign is that the host has totally corrected the original problem at
their end, but the bad news is that it may be hanging in one of the relay routers in the system due to erroneous information having been dumped on the system by the initial 'relapse'. If so, it may clear itself today, but if not, I may have to force a change in the NS IPs at the source (no, don't ask me to explain).
I'll keep an eyeball on it today and YOU keep feeding me trouble reports - just ensure you have flushed YOUR cache before you draw up a fresh page.
Jif