Impact of setting RegisterDNSARecords to 0 on AD domain controllers
Because we run our AD in our top level domain (for certain reasons) and we are running BIND as our DNS, we have the problem of windows domain controllers inserting A records directly against "domain.com".
Some research has indicated that one option is to set the registry value RegisterDNSARecords to 0 on all DCs to stop them registering A records against domain.com
What I wanted to get some feel for is what is the impact of removing these A records against the domain (both AD and internet top level) ?
Will there be any service impact in our AD environment ?
If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.