I'm trying to stop some SBCs (running Debian) from updating their time via the router's own NTP server. We just want to use a manually configured one such as one from
I believe the root cause to a particular problem occurs when some routers are reset. For a short time, the routers appear to be responding with blatantly wrong dates like 01 Jan 2003 (at time of writing it's 2019!), and then return to normal. This has a really negative impact on the software running on the respective SBCs. I have no control over these routers and really don't need to use them for NTP. It's just that the router's DHCP server offers NTP and the Debian SBCs use it automatically.
My first thought was to remove
request subnet-mask, broadcast-address, time-offset, routers, domain-name, domain-name-servers, domain-search, host-name, dhcp6.name-servers, dhcp6.domain-search, dhcp6.fqdn, dhcp6.sntp-servers, netbios-name-servers, netbios-scope, interface-mtu, rfc3442-classless-static-routes, ntp-servers;
But from what I can read
/etc/dhcp/dhclient.conf is no longer used by Debian as it uses
Every manual I can find says words to the effect:
Any per-interface NTP servers obtained from systemd-networkd.service(8) configuration or via DHCP take precedence.
This is specifically the behaviour I need to prevent. Even if the router can offer ntp-servers we need to prevent these being used as NTP servers.