DNS set in Win 10 22H2 to 1.1.1.1 (secondary 1.0.0.1). Event Viewer error on every boot: “NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on ‘time.windows.com,0x9’. The error was: No such host is known. (0x80072AF9)”
I changed system’s DNS settings to 8.8.8.8 and 8.8.4.4. Did a Restart from inside Win 10 and didn’t get that Time-Service Warning in Event Viewer>Windows Logs>System. Then did a full shutdown, powered on, and booted to desktop. Again, no Time-Service Warning in Windows Logs>System.
After the full shutdown and boot, I did get one “Information” level entry for Time-Service that says:
“The time provider ‘VMICTimeProvider’ has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well.”
I’ve put DNS back to 1.1.1.1 and 1.0.0.1 and will check again tomorrow after another cold boot…
That’s very strange! time.windows.com resolves fine over 1.1.1.1 as far as I can tell, so this is difficult for me to debug. Perhaps you could try running nslookup time.windows.com 1.1.1.1 in a Command Prompt (cmd.exe) to see if that finds an IP address?
It’s strange that it works with 8.8.8.8, but I suspect there’s something more going on here. Perhaps some other program or setting could be interfering, but I’m not a Windows expert; maybe someone else has an idea.
This is a recent issue since I’d never seen Time-Service give that “No such host is known.” warning in Event Viewer until past week or so.
If I open the Windows clock on the taskbar and click Sync Now, it instantly responds: “Successful”, so PC seems to be connecting to the correct IP address.
When I look up that IP address at iplookup[it says: “Couldn’t determine a hostname”.
So I wonder if Windows NtpClient isn’t recognizing the alias time.windows.com, but can still connect, rather than this being a DNS lookup issue…
I guess as long as the date/time can be synced, I probably should just ignore that warning in Event Viewer, unless somebody else has a better idea.
