home *** CD-ROM | disk | FTP | other *** search
- #
- # This file contains information that the soac command read
- # every time it runs.
- #
- # There are three types of information: SOA timers, valid interval
- # where the timers values have accepted and the time-out used when the servers
- # have queried.
- #
- # Replace every <value> according to your own needs.
- #
- # Comments begin with '#'.
- #
- #####################################
- ### SOA timers for top level domains:
- #
- ## REFRESH
- T_Refresh <value>
- #
- ## RETRY
- T_Retry <value>
- #
- ## EXPIRE
- T_Expire <value>
- #
- ## TIME TO LIVE (MINIMUM)
- T_TTL <value>
- #
- #
- #
- #################################
- ### SOA timers for other domains:
- #
- ## REFRESH
- Refresh <value>
- #
- ## RETRY
- Retry <value>
- #
- ## EXPIRE
- Expire <value>
- #
- ## TIME TO LIVE (MINIMUM)
- TTL <value>
- #
- #
- #
- #
- #######################################################################
- ### Error accept in the values of the SOA timers for top level domains:
- #
- ## for REFRESH
- DIFF_T_Refresh <value>
- #
- ## for RETRY
- DIFF_T_Retry <value>
- #
- ## for EXPIRE
- DIFF_T_Expire <value>
- #
- ## for TTL
- DIFF_T_TTL <value>
- #
- #
- #
- ###################################################################
- ### Error accept in the values of the SOA timers for other domains:
- #
- ## for REFRESH
- DIFF_Refresh <value>
- #
- ## for RETRY
- DIFF_Retry <value>
- #
- ## for EXPIRE
- DIFF_Expire <value>
- #
- ## for TTL
- DIFF_TTL <value>
- #
- #
- #
- #
- #
- #############################################
- ### Time-out used when the server has queried
- TIMEOUT <value>
- #
- #
- #
- ############## END OF TEMPLATE ##############
- #
- #
- ##########################################################################
- #
- # For help in the comprehension of these values we have reproduced below
- # a part of DNS-advice, wrote by Piet Beertema distributed with the BIND
- # package.
- #
- # ---------------------------
- # A problem I've found in quite some nameservers is that the various
- # timers have been set (far) too low. Especially for top level domain
- # nameservers this causes unnecessary traffic over international and
- # intercontinental links.
- # Unfortunately the examples given in the BIND manual, in RFC's and in
- # some expert documents give those very short timer values, and that's
- # most likely what people have modelled their SOA records after.
- #
- # First of all a short explanation of the timers used in the SOA record:
- # - Refresh: The SOA record of the primary server is checked
- # every "refresh" time by the secondary servers;
- # if it has changed, a zone transfer is done.
- # - Retry: If a secondary server cannot reach the primary
- # server, it tries it again every "retry" time.
- # - Expire: If for "expire" time the primary server cannot
- # be reached, all information about the zone is
- # invalidated on the secondary servers (i.e. they
- # are no longer authoritative for that zone).
- # - Default TTL: The default TTL value for all records in the
- # zone file; a different TTL value may be given
- # explicitly in a record when necessary.
- # (This timer is named "Minimum" in most examples,
- # but that name is highly confusing).
- #
- # For top level domain servers I would recommend the following values:
- # 86400 ; Refresh 24 hours
- # 7200 ; Retry 2 hours
- # 2592000 ; Expire 30 days
- # 345600 ; Default TTL 4 days
- #
- # For other servers I would suggest:
- # 28800 ; Refresh 8 hours
- # 7200 ; Retry 2 hours
- # 604800 ; Expire 7 days
- # 86400 ; Default TTL 1 day
- # but here the frequency of changes, the required speed of propagation,
- # the reachability of the primary server etc. play a role in optimizing
- # the timer values.
- # -------------------------------
-
-