The forward DNS entries ("A" records) for windows machines on the domain are populated automatically.However, the reverse DNS entries ("PTR" Records) are not.This article covers the default security settings for DNS zones: the settings are jacked up (or even if they are fine), you might try just blowing away the reverse zone and recreating it since you basically have a non-functioning reverse zone as it is...Try running an "ipconfig /registerdns" on one of the clients and see if it adds a record to the reverse zone.If they are in the forward zone but not the reverse, then something else is going on...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.
Uni Sim Design Suite is a powerful process modeling software that provides steady state and dynamic process simulation in an integrated environment.
Con press SIGN hemos podido ajustar, con seguridad, cada paso del proceso, lo que nos ha permitido, al final, obtener el certificado de Fogra en la ISO 12647-2.
Nuestros clientes han valorado el cambio, y las perspectivas de la empresa han mejorado.
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.