Dns slave server not updating andrea bowen dating
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.Then you can start numbering from one (or any convenient point). First, change the serial number on your primary master server and restart it; now the primary master server has the new integer serial number.Log onto one of your slave name server hosts and kill the ) and start up your slave name server.After modifying the zone data file becomes second nature, you'll make some "quickie" little change, forget to update the serial number . That's why you should use a tool that updates the serial number for you! Therefore, a number like 1.1 is converted to 10001 internally, and 1.10 is converted to 100010.This creates certain anomalies; for example, 1.1 is "greater" than 2, and 1.10 is "greater" than 2.1.
The first few times you make a change to a zone data file, you'll remember to update the serial number because the process is new and you're paying close attention. and none of the slaves will pick up the new zone data.
The next modification that day would change the serial number to 1997011501. It also has the advantage of leaving you an indication in the zone data file of when you last incremented the serial number.