We have an AD 2012 domain that's replicating fine. We used a Cisco product for DHCP, and our workstations etc register dns.
We have servers that are sometimes "forgetting" what a hostname resolves to. For example, I was troubleshooting a software configuration which allows one to limit which ip addresss and/or hostnames can see an admin page. This configuration didn't work, so from a command prompt I ping'd the workstation and I didn't get a response, most probably because of the virus protection firewall, but it did resolve the ip and attempt the ping.
I was working on this same issue, I got the software working, but then it stopped working. I called support and while talking to them I told them I could resolve the workstation with ping, but while talking i tried it again and all of the sudden
Ping request could not find host dt2137.domain.com. Please check the name and try again.
So I manually checked the forward lookup zone for each DC and the record is there. I went back to the server and did an nslookup and it looks up the host record fine. I go back to ping and I still can't ping the address.
I could run more commands like nbtstat -RR to flush cache or whatever, but that's just netbios not dns. So I think there is something about my understanding of dns that is lacking. Why can I nslookup but not ping. I know nslookup it's a similar but different query where you query a certain server. I don't understand why one gives results and the other doesn't.
This is a relatively new issue on our network, but I'm seeing it randomly pop up.
So in a nutshell ping worked, then an hour later from the same server didn't work. I don't get it.
Thanks,