 |  |
At 11:38 AM -0600 11/29/00, Philip Butler wrote:
Re: DNS Updates
From: Men & Mice Support
Date: Wednesday, November 29, 2000
Time: 1:34:49 pm
>After updates have been made to a Public DNS server, how long does it take
>for the news to spread so that other people (outside the network) can access
>using the URL assigned?
There are three issues involved.
1. Secondary service: A secondary server will try to update once
every x seconds, where x is determined by the Refresh value in the
SOA record (the Domain Information dialog in QuickDNS Pro Admin,
available from the Domain menu). Until that happens, the world will
get inconsistent results.
[To see more detail on this, consult the user manual or search the
list archives. The Retry and Expire fields are also involved.]
2. Time to Live: Every record has a TTL field. If left blank, a
default value is used, as set in the Minimum field of the SOA record.
The TTL is the maximum length of time for which the record should be
cached. After you make your change, more and more resolvers out in
the world will notice, as the old record expires. This does not
affect new records, since they didn't exist to be cached until the
update.
3. Non-compliant servers: Some resolvers cache records for longer
than they should, for up to several weeks. AOL is reputed to use such
broken DNS resolvers.
____________________________________________________________________
Chris Buxton Men & Mice
cbuxton@menandmice.com We Make DNS Easy!
Messages In This Thread:
Return to Digital Point Solutions' Home Page