Typical practice is to have one master, and one or two slaves which take their zone data from that master.
These instructions describe how to configure the slaves.
However, even when you use a tool, it is critical to know what goes on when the files are updated, so we'll start with the manual method.
After creating your zone data files initially, it should be fairly apparent what you need to change when you add a new host.
Any change requires time before it will be seen everywhere on the Internet.
But what many don't understand is that how fast or slow these updates are propagated is actually under their direct control through the SOA record. Although you have control over the speed that updates are propagated throughtout the Internet, they will never, ever, be instantenous! Your only control is over how short or long this delay will be.
Sometimes your users won't want to wait for the slaves to pick up the new zone data -- they'll want it available right away.
Something is always changing on your network -- new workstations arrive, you finally retire or sell the relic, or you move a host to a different network. First we'll discuss how to make the changes manually. Actually, we recommend that you use a tool to create the zone data files -- we were kidding about that wimp stuff, okay?
Each change means that zone data files must be modified. Or at least use a tool to increment the serial number for you.
We'll go through the steps here in case you weren't the one to set up those files or if you'd just like a checklist to follow.
Make these changes to your The primary master name server will load the new zone data.
Welcome to Linux Questions.org, a friendly and active Linux Community. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration.