I agree with the above suggestion.
And also, remember, even in a single server environment, the data you alter has to "Propagate" through several databases, as well as go out to all your machines, all over the same network, but not necessarily at the same instant -- not due to network speed as you might think, but rather to the timing mechanism for refresh rates (similar mechanism, but the values for when to refresh don't match the same moment in time; if it did the network might crash).
Network memory isn't like RAM or hardDrive space, it isn't written to instantly. It takes time, and in order to maintain speed, it makes assumptions. For instance, once you have a clean connection, connection sustain packets are constantly sent, but only to maintain the connection rather than holding actual data. Every 20min or so (wireless is typically 300-3600 seconds), the network connection refreshes, resending the data from your workstation machine, and verifying it with the server.
If there are changes, the changes are sent back.
But changes don't mean simple changes. For instance, have you ever tried to rewrite or delete a file in use by a system service? With some viruses, this was a boon to the virus. With system caching growing in popularity among systems, however, it's becoming less of a problem.
Here's what I'm talking about:
- When you try to edit the record list in the DNS, you are really just adding data to memory that is copied to the hard drive in "Temporary Cache", waiting to be appended.
- When the system closes and reopens the file for that program, there is a mark at the end, telling it to append the data you've altered, which loads it into memory as all one file, and utilizes it that way. Before closing the file, it rewrites the file back to the drive. This is the process that begins the linkage. The new information is useless until a file refresh and network refresh are complete.
The choice you have is how quickly you need it.
You have to either:
- Wait 20min to 2 days for it to carry over and refresh each database and connection
- Restart the service, which will then refresh every database and machine.