On our remote campuses we use a secondary net to back up the main server. This allows backups to go at Gbit speeds. The secondary net is using private IPs not reachable from any other systems.
The main server on this campus is running active directory DNS so if the connection to the main campus goes down, users can still do some things.
I discovered today I couldn't ping this server because the private IP has been distributed throughout our DNS environment and I was getting this address. I manually deleted the offending IP entry and it came right back.
How do I kill this entry permanently? Is there some way to keep DNS from accepting this IP or can I force the server to quit trying to register it?
March 30, 2006 8:56 PM
April 10, 2006 2:38 PM