DNS Basic test failured

I know this is an old thread - but it's high in the search results. Try re-running the test from an elevated command prompt. In some configurations I've seen the error only show in normal command prompts suggesting it isnt a full DNS error - just how it is being tested.

Hello,

Thank you so much for posting here.

As for the DNS management, it is strongly recommended to use domain controller as DNS servers. In single DC/DNS domain environment, DC/DNS server points to its private IP address as preferred DNS server in TCP/IP property.

If multiple DCs that’s the DNS servers are in a domain environment, recommendation to have all DCs point to ANOTHER/REMOTE DC’s IP address as preferred DNS and then point to it’s private IP address as an alternate DNS.

In an AD network we should only use your DCs as DNS servers. External DNS such as your gateway or 8.8.8.8 has no idea of the SRV records. Using them as DNS is what is incorrect.

Reference:
https://abhijitw.wordpress.com/2012/03/03/best-practices-for-dns-client-settings-on-domain-controller/

https://community.spiceworks.com/topic/2035647-gpo-status-says-ip-address-of-server-is-a-169-x-x-x

I would suggest we could have a check of the DNS configuration at first. Besides, here is the discussion about the similar DNS issue. Hope it is of some help to you.

Reference: https://social.technet.microsoft.com/Forums/windowsserver/en-US/0eb650c6-512f-4338-bd62-9ea543147928/dcdiag-testdns-fail-00000007-microsoft-virtual-machine-bus-network-adapter-has-invalid-dns?forum=winserverDS

Notes: Due to security, it is suggested not to post any logs here which contains the private information.

Please note: Information posted in the given link is hosted by a third party. Microsoft does not guarantee the accuracy and effectiveness of information.

Best regards,
Hannah Xiong

============================================
If the Answer is helpful, please click "Accept Answer" and upvote it.