Updating mx records in the dns

22 Mar

The zone has been delegated (via an NS Resource Record) to this DNS.

The term master was introduced with BIND 8.x and replaced the term 'primary'.

Example configuration files for a master DNS are provided.

A Slave DNS gets its zone data using a zone transfer operation (typically from a zone master) and it will respond as authoritative for those zones for which it is defined to be a 'slave' and for which it has a currently valid zone configuration.

Slave status is defined in BIND by including 'type slave' in the zone declaration section of the file as shown by the following fragment.If a DNS server receives a query for a zone for which it is neither a Master nor a Slave then it will act as configured (in BIND this behaviour is defined in the file): A master DNS server can NOTIFY zone changes to defined (typically slave) servers - this is the default behaviour.NOTIFY messages ensure zone changes are rapidly propagated to the slaves (interrupt driven) rather than rely on the slave server periodically polling for changes.Assuming NOTIFY is allowed in the master DNS for the zone (the default behaviour) then zone changes are propagated to all the servers defined with NS Records in the zone file.Other acceptable NOTIFY sources can be defined using the also-notify parameter in Read it only when accompanied by your favorite keep-me-awake-cos-I-can't-take-anymore-of-this-stuff beverage.