I have a system (SYSTEMX) that is connected to our network through a VPN. Periodically the VPN gets disconnected and SYSTEMX loses its connection to the network. When this occurs I usually easily find out from a log generated during a nightly task that fails as a result of the sytem being offline.
I ping the system "ping SYSTEMX" and get timeouts as expected. Reconnect the VPN and it is good to go.
Two times however the log has had different results as a new system (SYSTEMSTEALTH) will come in and resolve to the same IP address that SYSTEMX was given.
I ping "ping SYSTEMX" and lo and behold responses come in.
When I do an "nslookup SYSTEMX" and "nslookup SYSTEMSTEALTH" both names resolve to the same IP address.
I am not an expert on network topology however it seems to me that upon distributing a new DHCP lease there should be communication to the name server to remove stale entries for that address to prevent this type of scenario.
Does anyone have any suggestions or are able to clarify a way to prevent this from occuring? I am working with my IT deptartment to resolve this issue, their current stance is that it is fine as SYSTEMX is not on the network SYSTEMSTEALTH comes in after and all is good. However being able to "ping SYSTEMX", connect to it, file share to it using admin shares; this does not seem right to me since SYSTEMX is really SYSTEMSTEALTH.
Thank you for your help.