Domain controller DNS should point to itself in order to optimize DNS lookup performance. This is because the AD DS server is the authoritative source for the AD domain. If the AD DS server is not available, then DNS queries for the AD domain will be directed to the local DNS server.
If the local DNS server is not able to resolve the AD domain name, then the query will be forwarded to the AD DS server. By directing all DNS queries to the AD DS server, the AD domain name will be resolved more quickly.
4 Related Question Answers Found
Domain Controllers should use themselves for DNS. There are several reasons why this is the best practice. First, it is a best practice to have a single point of administration for your DNS.
Domain controllers are servers that act as the primary control point for a domain, and are responsible for ensuring that all DNS requests are handled correctly. By running DNS on a domain controller, you can ensure that all requests are handled correctly and that your domain is fully operational. However, there are a few drawbacks to running DNS on a domain controller.
DNS Needs to Be on a Domain Controller
There are a few reasons why DNS needs to be on a domain controller. First and foremost, DNS is a critical service that is used to resolve domain names into IP addresses. If DNS is not running on a domain controller, then users will not be able to access their domain names or other resources.
A common question is whether domain controllers should be DNS servers. In general, the answer is no. Domain controllers should not have the responsibility of providing DNS service for the domain.
