On Sat, May 16, 2020 at 05:07:59PM +0100, an0nym wrote:
> Hello,
> 
> I hope you are safe and well.
> 
> When dnsmasq is configured to monitor hostsdir, I believe there is no
> forgetting logic when you delete and then create or simply overwrite one of
> the files there with different filter and the same allocated IP.
> 
> E. g.
> 
> # grep -F dhcp-hostsdir /etc/dnsmasq.conf
> dhcp-hostsdir=/etc/dnsmasq.d/hosts.d
> # echo "id:test,192.168.0.156" >/etc/dnsmasq.d/hosts.d/test.conf

    test   .156


> # systemctl status dnsmasq
> ...
> dnsmasq[21376]: inotify, new or changed file
> /etc/dnsmasq.d/hosts.d/test.conf
> dnsmasq-dhcp[21376]: read /etc/dnsmasq.d/hosts.d/test.conf
> # echo "id:test2,192.168.0.156" >/etc/dnsmasq.d/hosts.d/test.conf

    test2    .156


> # systemctl status dnsmasq
> ...
> dnsmasq[21376]: inotify, new or changed file
> /etc/dnsmasq.d/hosts.d/test.conf
> dnsmasq-dhcp[21376]: read /etc/dnsmasq.d/hosts.d/test.conf
> dnsmasq[21376]: duplicate dhcp-host IP address 192.168.0.156 at line 1 of 
> /etc/dnsmasq.d/hosts.d/test.conf

    duplicate  of .156


> Dnsmasq 2.80. Apologies if this has been fixed in 2.81,
> I did not succeed in compiling from sources to check.
> 
> I hope this helps.

Helpfull is reporting back how helpfull this message was.


Groeten
Geert Stappers
-- 
Silence is hard to parse

_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

Reply via email to