I've had issues similar to this once in a while, but not quite like this. When I try to ping a hostname, I get an IP address for that machine, but the trouble is, that IP address actually belongs to another machine. For example: If I had two machines, one named win2000 and the other win7pro; I ping win2000 and it returns an IP of 172.16.145.1. When I ping win7pro, it also returns the IP of 172.16.145.1. When I use remote desktop or VNC to connect to win2000 using the hostname, I get logged in, only to find that the machine I have logged into is actually win7pro and not win2000. If I check DHCP I find the address for win200 is actually 172.16.145.10 and the machine shows the correct IP also when I login with RDP or VNC. I tried checking my DNS server entries and DHCP. DHCP reports the correct hostname associated with the correct IP address, but DNS sometimes will not even have a DNS entry for the hostname. I have two DNS servers running server 2k8 standard. Both have active directory. My primary DC also runs DHCP. For some reason, it seems that DNS is not properly pointing the IP addresses to the correct machine. Is there any way to reset the DNS on my workstation other than ipconfig /flushdns to make sure it's all cleared out and clean? Or does my machine always check my DNS servers for the appropriate entries every time you use the DNS name? Thanks. Addendum: I've also found that my forward lookup zone sometimes contains multiple hostnames for an IP address. I had set the scavange and aging records to 7 days. Why does DNS keep entries for IP addresses that are no longer valid according to DHCP?

Hello, Is your DHCP the Win server or a separate router? Are your two DNS server's zones AD Integrated? Do the host records on DNS1 and DNS2 match? Do you have enable automatic DNS updates? Miguel Miguel Fra / Falcon IT Services Computer & Network Support, Miami, FL Visit our Knowledgebase and Support Sharepoint Site

Hi, Thanks for posting here. What if test via FQDN of remote computer, would this issue persist ? Is this issue occurred on all clients ? Please take look the suggestion in the article below first : Wrong or Inconsistent Answer If you get the wrong answer when looking up a local name or you get an inconsistent answer, depending on which name server you ask or when you ask, first check the synchronization between your name servers: Are they all holding the same serial number for the zone? Did you forget to increment the serial number on the primary after you made a manual change (problem 1)? If you did, the name servers may all have the same serial number, but they will answer differently out of their authoritative data. Did you forget to restart the primary after making a manual change (problem 2)? Then the primary will return (via nslookup, for example) a different serial number than the serial number in the zone data file. Are the slaves having trouble updating from the primary (problem 4)? Is the name server's round-robin feature rotating the addresses of the domain name you're looking up? If you get these results when looking up a name in a remote zone, you should check whether the remote zone's name servers have lost synchronization. You can use tools like nslookup to determine whether the remote zone's administrator has forgotten to increment the serial number, for example. If the name servers answer differently from their authoritative data but show the same serial number, the serial number probably wasn't incremented. If the primary's serial number is much lower than the slaves', the primary's serial number was probably accidentally reset. We usually assume a zone's primary name server is running on the host listed as the origin in the SOA record. You probably can't determine conclusively that the primary hasn't been restarted, though. It's also difficult to pin down updating problems between remote name servers. In cases like this, if you've determined that the remote name servers are giving out incorrect data, contact the zone administrator and (gently) relay what you've found. This will help the administrator track down the problem on the remote end. Troubleshooting DNS http://technet.microsoft.com/en-us/library/bb726934.aspx Thanks. Tiger LiPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.