Re: timedatectl DHCP NTP Server

[john doe]

On 2/5/2021 4:10 AM, Charles Curley wrote:

On Thu, 4 Feb 2021 22:16:12 +0100
basti <mailingl...@unix-solution.de> wrote:

I use a up to date debian. As I can see now timedatectl seems *not*
using the NTP Server provide by DHCP. I have configure a NTP server
in  LAN.

timedatectl  timesync-status
        Server: 167.86.86.192 (0.debian.pool.ntp.org)
Poll interval: 1min 4s (min: 32s; max 34min 8s)

I see the same, on a Bullseye system.

root@dragon:~# timedatectl  timesync-status
        Server: 198.74.51.125 (2.debian.pool.ntp.org)
Poll interval: 34min 8s (min: 32s; max 34min 8s)
          Leap: normal
...

This box is running systemd, and ntp is not present.

The dhcp server shows:


subnet 192.168.100.0 netmask 255.255.255.0 {
     option subnet-mask 255.255.255.0;
     option broadcast-address 192.168.100.255;
     option routers 192.168.100.31;
     option domain-name-servers 192.168.100.30, 192.168.100.6, 192.168.100.31; 
# chaffee, hawk, freeman
     option domain-search "localdomain", "virtual", "yen";

     option domain-name "localdomain";
     option ntp-servers 192.168.100.31; # freeman, AKA ntp.localdomain
     # range 192.168.100.1 192.168.100.254;

...

It does work fine for me, is the lease showing the ntp server?

Note that systemd is using a sntp client and not a ntp client.

Does 'systemctl restart systemd-timesyncd' help?

--
John Doe