Le ven. 3 août 2018 à 19:18, Simon Kelley <[email protected]> a écrit :
> The serial number is initialised when dnsmasq starts up to the current > time (seconds since 1st Jan 1970). > > > If your serial starts a one each time dnsmasq starts up then something > is wrong. Maybe dnsmasq is started before the time is set in your machine? > > I run it on a "normal" server, the time is maintained via ntp (chrony actually). The problem is there when I restart dnsmasq as well: root@srv:~# dig @127.0.0.1 swtk.info soa | grep SOA swtk.info. 600 IN SOA . . 15 1200 180 1209600 600 root@srv:~# systemctl stop dnsmasq.service && systemctl start dnsmasq.service root@srv:~# dig @127.0.0.1 swtk.info soa | grep SOA swtk.info. 600 IN SOA . . 1 1200 180 1209600 600 root@srv:~# systemctl stop dnsmasq.service && systemctl start dnsmasq.service root@srv:~# dig @127.0.0.1 swtk.info soa | grep SOA swtk.info. 600 IN SOA . . 1 1200 180 1209600 600 root@srv:~# date +'%s' 1533316912 I do not know how the first serial ended up being 15, but a restart sets it at 1. Cheers Wojtek
_______________________________________________ Dnsmasq-discuss mailing list [email protected] http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
