Best Practices Domain Controller use self DNS Registration or use static host entry?

Question

On a Domain Controller, there are two thoughts on DNS entry in the domain forward lookup group. One line of thought is to create a static host (A) entry for the Domain Controller(s) in the domain Forward lookup. This is in addition to the default entries that automatically create for NS etc. The other line of thought is to check mark "Register this connection's address in DNS" in the DNS Tab in advanced settings for TCP/IP in adapter settings and let the controller maintain its own entry. I have configuring DNS both ways over time, and in each instance got different BPA (Best Practices) or other errors as a result. I'd like some thoughts on how other admins think about this. It is on a local private domain where the computers do not need to be reached from the outside Internet. Thanks in advance.

Answer 1

Hello!

While dynamic DNS registration can be convenient for end-user devices with dynamic IP addresses, for infrastructure components like DC which IP addresses are static and unlikely to change, static DNS entries may be appropriate. Static entries help maintain network reliability. Stability is crucial. We won't have to deal with unexpected changes in IP addresses.

Thanks,

Karlie

Answer 2

Thank you. I believe you indicated that on a domain where controllers and member servers don't ever change IP addresses, using static host entries in DNS is acceptable, which would also imply it is therefore safe to ignore the DNS BPA entry that the host DC isn't set up to register itself each time it boots.