Dynamic DNS Zones

From Freelock Knowledge Base

When a zone is being updated dynamically with BIND nsupdate or DHCP, you cannot just edit the zone file without breaking the zone. If you attempt to update a zone that is being dynamically updated, the DNS server won't load the zone, and will not answer DNS queries for that zone. This could, obviously, be a bit of a problem...

Two solutions: either use a global key to manage the zone with nsupdate, or freeze updates while you edit the zone file manually.

Contents 1 Manage zone with nsupdate 2 Freeze the zone 2.1 Bind 9.2 - 2.2 Bind 9.3 +

[edit] Manage zone with nsupdate

This takes setting up a key on the server to allow updates, and learning how to use nsupdate. While we've tested this a few times, we don't actually use it.

[edit] Freeze the zone

BIND 9.2 and earlier can't freeze. You have to stop the server, edit the zone file, delete the journal, and restart the name server.

[edit] Bind 9.2 -

1. rndc stop
2. rm /var/named/*.jnl
3. edit zone files, don't forget to increment serial number
4. service named start

[edit] Bind 9.3 +

1. rndc freeze zonename.com
2. edit zone files, don't forget to increment serial number
3. rndc unfreeze zonename.com