On a new Windows 2019 server, the root hints are configured with IP v.6 IP addresses. I validated against the known root hints available at IANA (https://www.iana.org/domains/root/servers
) and they are all correct. Yet, when I run the Best Practices Analyzer I get multiple warnings related to these IPv6 root hints that they must respond NS queries for the root zone. The server is a single domain controller and the DNS server for a new office that I am setting up. I have entered several public DNS servers in the Forwarder tab (e.g. Google DNS, OpenDNS, Level 3 DNS). The check box for "Use root hings if no forwarders are available" was checked and I left it checked.
When I initially setup the server, I ran then commands to change the priorities of IPv4 over IPv6. The office will use IPv4 (small office with 15 computers) but Ip v6 is enabled by default, and I see no reason to change it.
As I am not a DNS expert, I have a few questions on these root hints in the IPv6 format.
1. I know they exist in the C:\WINDOWS\system32\dns\ca
che.DNS in both formats, IPv4 and IPv6 - see attached cache.dns.txt file. Why are the IPv6 entries appearing the Root hints Tab in the DNS properties - see attached screenshots? Why aren't the IPv4 IP addresses appearing instead? Especially since I changed the priority from IPv6 to IPv4.
2. What is it required to eliminate the warnings shown by the Best Practices Analyzer? From reading multiple posts here I get it that they are benign, and don't hurt, especially since root hints are the last resort for DNS resolution if all forwarders fail. But, as I am setting up this new server, I would like to minimize the numbers of those benign errors that Microsoft throws our way with no explanation/fix under than "don't worry about that".
Any feedback would be very much appreciated. Thank you for your assistance.