I didn't even think about the TTL. Unfortunately the old one was set to
1209600, which is 14 days. Seems awful long to me. I guess they'll just have
to wait it out.
Thanks Scott,
Mike Perdue
WebMaster
The Grizzard Agency - An MSGi Direct Company
[EMAIL PROTECTED]
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 19, 2000 4:16 PM
To: [EMAIL PROTECTED]
Subject: Re: [IMail Forum] Strange DNS problem, slightly Off Topic
> The problem is the changes have not propagated properly. I've done
> MX lookups on many name servers, and only about half of them have
> picked up the changes (i.e.. they don't see the A record or the MX
> record, but they still see the original "www" A record).
If some of them *do* see the changes, then I think everything is correct on
your end at this point.
This is caused by the *OLD* timeout value you had, before making the change.
The DNS servers out there that have cached your old DNS entries have the old
TTL (time to live) value, and that timeout value hasn't timed out yet. For
example, if it was set to a week, and it got the old value 3 days ago, it
will hold on to the old values for another 4 days.
Changing the serial number won't do anything for the DNS servers. That only
affects *your* DNS servers (they will check every so often (as determined by
the SOA record) to see if the serial number has changed, and if so, re-load
everything).
When you set a TTL value too high, and then lower it, you just have to sit
and wait for the DNS servers to get the new record.
-Scott
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
