# rndc reload foo.example bar.example
Remember to increment the serial number in your zone's SOA record after changing the zone data. The primary master reloads the zone regardless of whether you've incremented the serial number, since the file's modification time has changed, but your zone's slaves only have the serial number to tell them whether the zone has been updated.
Reloading individual zones, as shown
above, was introduced in BIND 8.2.1 and again in 9.1.0. With older
versions of BIND, just use
rndc reload or
ndc reload, as appropriate. That takes a little
more time, since the name server checks all zone data files to see
which have changed.
If you're reloading a zone that exists in multiple
views on a BIND 9 name server, specify the view with
reload domain-name-of-zone class view. For example:
# rndc reload foo.example in external
Learn more about this topic from DNS & Bind Cookbook.
The DNS & BIND Cookbook presents solutions to the many problems faced by network administrators responsible for a name server. This title is an indispensable companion to DNS & BIND, 4th Edition, the definitive guide to the critical task of name server administration. The cookbook contains dozens of code recipes showing solutions to everyday problems, ranging from simple questions, like, "How do I get BIND?" to more advanced topics like providing name service for IPv6 addresses.