Problem with synching to time server

When looking through the list of events in Windows Event Viewer, I have, for a long while now, been getting, every day, several warnings that look like this:-

Event 134, Time service
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time-new.nist.gov'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9).

The most recent of these was today at 15:28. When I look at the internet time settings (via control panel), it says the clock was successfully synchronised with time.nst.gov on 22/10/2018 (today) at 16:19 (a few minutes ago). The list of time servers is as follows:-

time.windows.com
time.nist.gov
time.nw.nist.gov
time-a.nist.gov
time-b.nist.gov

My questions is this: Why is the NTP client apparently trying to synchronise using a server that isn’t in the list? Where is it getting the server name 'time-new.nist.gov' from? It’s not in the list - only ‘time.nw.nist.gov’.
If I set the time server to time.windows.com should it cure the problem?