Windows dhcp not updating dns records adult dating orangeville ohio
The DHCP server in this case is NOT a windows server. The only thing I had to do after this was, flush the dns entries on the clients with: ipconfig /flushdns After this they have poped up in my reverse lookup zone. The fix of adding the DHCP server to DNSupdateproxy group solved my issues.
3) If the issue is that your reverse zones are mismatched between domain controllers (meaning a host was able to register with one of the DCs, but the registration did not get replicated to the others) it could mean the zones themselves aren't replicating between domain controllers.Make sure the reverse zone is AD-Integrated and also check the Zone Transfers tab and make sure they are allowed (generally Only to servers listed on the Name Servers tab).Also make sure your DNS server are listed on the Name Servers tab. Ok so given that your DHCP server is not registering the records on behalf of the clients, and aside from your windows clients not being set to register with DNS on their NICs (which you should verify in TCP/IP properties on the client NIC), I would check the security settings on your reverse zone to make sure clients are allowed to register in the reverse zone.This user's credentials are used in the Advanced - Credentials setting of the DHCP zone.What I am finding is that workstations that are joined to the domain are showing up in DNS just fine, while workstations that are not part of the domain do not show up in DNS - however they do show up in DHCP.