On 06.03.22 07:22, Alkis Georgopoulos wrote:
aren't bind-dynamic and bind-interfaces for people that have multiple
services in the 53 port?
It does not matter here. There may and may not be other programs, dnsmasq
or not, listening on 53 port on different interfaces.
I have a single dnsmasq running, and it's listening on 0.0.0.0:53,
i.e. on "all interfaces", shouldn't it be answering?
not if you configure it only to listen on specific interfaces.
Without --bind-interfaces dnsmasq sits on 0.0.0.0 but only answers on
interfaces it is configured to listen on.
I think it's a wrong initialization bug somewhere in the code that
decides when dnsmasq should answer. Configuration workarounds do
exist, but I feel that it's a bug that should be resolved by updating
the dnsmasq codebase.
this is the standard dnsmasq behaviour when new interface appears and you
don't specify --bind-dynamic to detect them.
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
REALITY.SYS corrupted. Press any key to reboot Universe.
_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
