Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #268085

Re: Temporary failure in name resolution

Show all headers | View raw

Shaheena Kazi wrote: 
> Package: ntpsec
> 
> Hello, we were using Bullseye and have upgraded to Bookworm.
> With Bookworm, we have ntpsec.
> The package is installed successfully and the service looks good.
> But the syslog is filled with below messages:
> ++++++++++++++++++++++++
> 2024-03-06T14:58:11.724851+05:30 hostname-shaheena ntpd[35823]: DNS:
> dns_check: DNS error: -3, Temporary failure in name resolution
> 2024-03-06T14:58:11.724862+05:30 hostname-shaheena ntpd[35823]: DNS:
> dns_take_status: None=>temp, 3
> 2024-03-06T14:58:19.572547+05:30 hostname-shaheena ntpd[35823]: DNS:
> dns_probe: None, cast_flags:1, flags:20801
> 2024-03-06T14:58:19.588607+05:30 hostname-shaheena ntpd[35823]: DNS:
> dns_check: processing None, 1, 20801
> 
> In ntp.conf the server is always set to None. We keep it to None always.

Did you name a machine "None" in /etc/hosts or your local DNS?

NTP does not work without either an authoritative clock or a
remote NTP server - preferably a pool of NTP servers. Do you
have an authoritative clock source, such as a GPS receiver or an
atomic clock?

Please show us your complete ntp.conf


-dsr-

Back to linux.debian.user | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Temporary failure in name resolution Shaheena Kazi <shaheena.kazi@gmail.com> - 2024-03-06 11:20 +0100
  Re: Temporary failure in name resolution Dan Ritter <dsr@randomstring.org> - 2024-03-06 11:40 +0100

csiph-web