Monitor DNS Zone Reload

Luke Hebert

- 2 minutes read - 219 words

When a DNS zone file changes on disk, the running named daemon does not pick up the change automatically. You need to tell it to reload the zone, and then verify that the reload actually succeeded. Two commands handle both steps.

Triggering the Reload

Run rndc reload (or rndc reload <zone-name> to target a specific zone). This signals the named process to re-read its zone files from disk without dropping existing connections.

rndc reload

If you only want to reload one zone, pass the zone name:

rndc reload example.com

Confirming the Reload

Immediately after, tail the system log to confirm named logged the reload event:

tail /var/log/messages

Look for a line similar to:

named[1234]: zone example.com/IN loaded serial 2022012401

The serial number should match the one in your updated zone file. If you see an error such as zone ... failed to load, the zone file has a syntax problem and the old data is still being served.

Quick Checklist

  • Edit the zone file and bump the serial number.
  • Run rndc reload (or rndc reload <zone>).
  • Tail /var/log/messages and confirm the new serial loaded.
  • If the reload fails, run named-checkzone <zone> /path/to/zonefile to pinpoint the syntax error.

This two-command pattern keeps your DNS changes verifiable in seconds rather than waiting for a TTL to expire.