dhcpcd-discuss

Re: "nooption dhcp6_name_servers" not (fully?) working

nighthawk

Tue Jan 14 20:45:46 2020

On Tue, Jan 14, 2020 at 1:27 PM Roy Marples <roy@xxxxxxxxxxxx> wrote:
>
> I don't see how DNS will restart NTP.
> However, that dhcpcd version does request NTP by default, but it should only
> restart NTP if the configuration has changed.

Thats unexpected. I thought it would fire every time, regardless if
the information changed or not. Cool stuff!

> Newer versions do not request NTP.
> Try commenting out "option ntp_servers" in /etc/dhcpcd.conf

Good idea, I just tried that. My config now looks something like this:

option rapid_commit
option classless_static_routes
option interface_mtu

interface eth0
        static ip_address=192.168.0.7/24
        static routers=192.168.0.1
        static domain_name_servers=192.168.0.1 2a02:908:2:a::1 2a02:908:2:b::1
        dhcp6
        nooption ntp_servers, dhcp6_ntp_server, dhcp6_name_servers

Unfortunately my NTP service is still being restarted every 15 seconds.

I looked at the relevant packets and see, that dhcpcd is indeed not
requesting NTP or DNS information anymore - and the router is honoring
this. I am now even more puzzled, why the hook script keeps being
called.

As soon as I set "nohook timesyncd.conf" the restarts stop - so it's
definitely dhcpcd causing it. Any other ideas?

Follow-Ups:
Re: "nooption dhcp6_name_servers" not (fully?) workingRoy Marples
References:
"nooption dhcp6_name_servers" not (fully?) workingnighthawk
Re: "nooption dhcp6_name_servers" not (fully?) workingRoy Marples
Archive administrator: postmaster@marples.name