Hi, Actually, there is probably another explanation for this particular case, a much simpler one. Was your client's ISP also the former web host? (or using the same DNS servers) ? If so, they simply had not gotten around to deleting the DNS zone files for your client's domains, but had deleted the website itself. And the moment they did delete the zone files, probably when your client called them, the problem was "fixed".
We see this crop up regularly from time to time. Nothing to do with caches, insanely long TTL's, Verisign, ICANN, compressed or uncompressed root zone or gtld files, DNS or BIND. Just plain laziness or organizational red tape or some slip up in their process. best regards Mike. On Sat, 22 Jun 2002, wxWeb.com wrote: > Saturday, June 22, 2002, 6:29:45 PM, POWERHOUSE wrote: > > More like UPDATING the database, that would answer the question as to WHY > > some ISP's can see a new nameserver within 24 hours, and others cannot for > > up to 3 or 4 days. > > So what you are seeing is the customer's ISP having cached the data > for a long period of time, because the previous administrator of the > DNS they were using set an excessively long TTL period for that dns > zone, resulting in caching of the data for a much longer than normal > period. > > It has nothing to do with the ISP needing to do an update or download > anything.
