SOLVED: Microsoft PowerShell cmdlet Get-DnsServerRootHint shows error No root hint found by {server} name server on {servername} server

When you run the Microsoft PowerShell cmdlet Get-DnsServerRootHint you see the error 

No root hint found by {server} name server on {servername} server



When you view the root hints in the DNS server manager MMC you see the root hint listed as "Unknown".


If the DNS server is Active Directory Integrated this could be because the record is corrupt.

You can view the raw data using ADSIEdit.msc and going to the following (replacing the distinguished name of the domain as required).

DC=RootDNSServers,CN=MicrosoftDNS,DC=DomainDnsZones,DC=demo2019,DC=int



Check the dnsRecord value if this value is missing or corrupt it will display the error above.



If the DNS server is not Active Directory integrated then an error may be found in the cache.dns file found by default in the following location:
C:\Windows\System32\dns\cache.dns

The correct value can be set by clicking the "Edit" button in the DNS manager MMC and entering the correct value, or by clicking "Remove" if the value should not exist.


The PowerShell cmdlet should now work as expected.


Why not check out our DNS server documentation tool

XIA Configuration Server?








Comments

Post a Comment

Popular posts from this blog

Windows Server 2016, 2019, 2022, Windows 10 and Windows 11: Date and time "Some settings are managed by your organization".

Image
When you're using the new "Modern" date and time settings in Windows Server 2016, 2019, 2022, Windows 10 and Windows 11 you may find that you can't set the correct date and time and the value "Some settings are managed by your organization". - While you're here - Why not check out our Windows Server Documentation and Audit Tool? The simplest way around this is to go back to the proper control panel using Start, Run, "Control.exe" and searching for "Set the date".  Within here you can set the date and time manually as required If you try and click the Change time zone button you may again get access denied... To resolve this open an elevated command prompt by right clicking the command prompt and selecting Run as Administrator  From there run the command rundll32.exe shell32.dll,Control_RunDLL timedate.cpl This will open the Data and Time control panel app elevated as an Administrator.
Read more

TFTPD32 or TFTPD64 reports Bind error 10013 An attempt was made to access a socket in a way forbidden by its access permissions.

Image
When you start the trivial FTP (TFTP) server application TFTPD32 or TDTPD64 you may see the following error Bind error 10013 An attempt was made to access a socket in a way forbidden by its access permissions. This can be because another application is using this port. The easiest way to check if (and which) application is using the port is as administrator run an elevated command prompt and enter netstat -anb > ports.txt Then open ports.txt in Notepad and search for :69, you'll quickly be able to see the process using the required port - While you're here - Why not check out our Windows Server Documentation and Audit Tool?
Read more

Windows Server 2019 desktop icons such as My Computer, Windows cannot access the specified device, path, or file.

Image
In Windows Server 2019 you may notice that the desktop icons such as My Computer are missing, however when you goto Personalization > Themes > Desktop icon settings You see the error Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item. The quickest way to resolve this is to ignore the modern UI and desk.cpl ,5 From here you can easily add the My Computer icon - While you're here - Why not check out our Windows Server Documentation and Audit Tool?
Read more