User Tools

Site Tools


hwmig2007dns

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

hwmig2007dns [2015/06/09 15:23] (current)
Line 1: Line 1:
 +[[:TuxSoftware]]
 +
 +On the old machine, named runs as nobody. On the new machine, it installed wanting to run as bind. We can accept this change.
 +
 +The pid-file has moved - we can accept this change.
 +
 +bind9 runs, and tries to send notifies.
 +
 +dig returns the right ip address (ie, the address of the real tux)
 +
 +Seems good enough.
 +
 +===== SOA record =====
 +
 +| **field** | **example** | **normally** | **prep for change** |
 +| **serial number** | 2003080800 | 2005070201 | 2007051700 |
 +| **refresh** | 2 d - 172800 | 3 h - 10800 | 10 m - 600 |
 +| **update retry**  | 15 m - 900 | 1 h - 3600 | 5 m - 300 |
 +| **expiry** | 2 w - 1209600 | 1 w - 604800 | 1 w - 604800 |
 +| **minimum** | 1 h - 3600 | 1 h - 3600 | 10 m - 600 |
 +
 +See http://www.ripe.net/ripe/maillists/archives/dns-wg/1998/msg00070.html for info on these values.
 +
 +  * refresh:
 +
 +Secondaries check every <refresh> seconds, whether the SOA on the primary has changed. If yes, a zone transfer is done.
 +
 +  * retry:
 +
 +A secondary having been unable to do a zone transfer because of unreachable of the primary retries every <retry> seconds.
 +
 +  * expire:
 +
 +The zone's information is considered invalid by the secondary if the primary could not be reached for <expire> seconds.
 +
 +  * minimum TTL:
 +
 +This is the default value for all records in the zone file which can be overriden by values for the individual records. After <minimum TTL> seconds, the zone information on the caching nameserver becomes invalid and has to be re-fetched from an authoritative server. NOTE: This field was intended to be a minimum value for all records in the zone but is now widely implemented as giving the default.
 +
  
hwmig2007dns.txt ยท Last modified: 2015/06/09 15:23 (external edit)