Conflicts with DNS Records and IP Addresses When pinging an old computer, it might erroneously show as online due to the DNS Host A records on Server-DC2. One specific issue happened when determining if BRPNB136 was online. The screenshots in the example show use of elevated Command Prompt on client computer as well as DNS Manager on Server-DC2. Pinging BRPNB136 is returning an IP address, and thus indicates that the computer is online. However, connecting to it through Remote Desktop didn’t work, so performing a ping –a on the IP address was done. This ping returned hostname VISTAMACHINE4 instead of the expected BRPNB136. The ping results indicates that there is something wrong in the DNS records on Server-DC2. There is likely a stale record of BRPNB136 pointing to the IP address that VISTAMACHINE4 currently is using. The Reverse Lookup Zones section appears to contain the correct record. Checking Forward Lookup Zones next. There is actually another computer with the same IP address. Pinging it. The DNS A records on Server-DC2 contains two stale records for IP address 10.222.113.65. You can see from the Timestamp that BRPNB136 and BRPNB164 are old records. We can check DHCP to verify that VISTAMACHINE4 is the valid one. We are can safely delete the old A records for BRPNB136 and BRPNB164 in DNS Manager. The following commands need to be executed on the client computer for the changes to take effect right away:ipconfig /registerdns ipconfig /flushdns The computers no longer answers ping.