Master and slave dating

Slave operation can also be programmed using several command is especially useful as it triggers an immediate retrieval of the zone from the configured master. For the BIND backend, the native BIND configuration language suffices to specify multiple masters, for SQL based backends, list all master servers separated by commas in the 'master' field of the domains table.Since version 4.0.0, Power DNS requires that masters sign their notifications.because the master is offline, Power DNS will retry the domain after seconds between checks.With default settings, this means that Power DNS will back off for 1, then 2, then 3 etc.To resolve this issue, Power DNS tries multiple tactics to figure out the IP addresses of the slaves, and notifies everybody.In contrived configurations this may lead to duplicate notifications being sent out, which shouldn't hurt.

Consult the documentation for your backend to see how it processes changes in zones.All slaves for this domain must receive a notification but the nameserver only knows the names of the slaves - not the IP addresses, which is where the problem lies.The nameserver itself might be authoritative for the name of its secondary, but not have the data available.Power DNS assumes that the backend is taking care of replication unaided.My SQL replication has proven to be very robust and well suited, even over transatlantic connections between badly peering ISPs.To help deal with slaves that may have missed notifications, or have failed to respond to them, several override commands are available via the On launch, Power DNS requests from all backends a list of domains which have not been checked recently for changes.

You must have an account to comment. Please register or login here!