[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cobalt-users] propagation..
- Subject: RE: [cobalt-users] propagation..
- From: Jeff Lasman <jblists@xxxxxxxxxxxxx>
- Date: Thu Feb 10 14:00:45 2000
At 04:39 PM 2/10/00 -0500, you wrote:
While I have your attention, <evil grin>, that TTL of 86400 means that any
site should check the DNS after one day for an update?
Absolutely.
If so, and that is
the TTL that was set on all my domains, which is why I can't understand why
@Home's DNS servers were caching the info for 5 days when the root
nameservers had the update already.
My question exactly, already stated in this very thread, I think <smile>.
The strange thing is, when I sent through a slew of changes, 20 domains
would update properly after one day, 1 out of them wouldn't. @Home's tech
support was baffled while on the phone. Of course by the time they replied
to my email, 5 days later, the DNS had finally updated.
The only thing I can think of is that perhaps you didn't update the serial,
and your old TTL was five days, and one person from @Home happened to read
your DNS the moment your primary was down, and got your secondary? Or
maybe your TTL was correct, but five people did it over a period of five
days? I DON'T THINK SO <wry grin>.
Your guess is as good as mine <smile>.
Cricket Liu, one of the authors of "DNS and BIND" can be hired, for some
awfully huge some of hundreds of dollars an hour (or so I've been
told). I'm sure he could figure it out. Is it worth it? Maybe if
amazon.com or ebay.com has to renumber, it might be, but to me, frankly, NO
<smile>.
Jeff
--
Jeff Lasman <jblists@xxxxxxxxxxxxx>