[Dnsmasq-discuss] Problem with no-resolv and no IP

Alkis Georgopoulos alkisg at gmail.com
Sun Mar 6 17:11:32 UTC 2022


Hi Matus,

 > Without --bind-interfaces dnsmasq sits on 0.0.0.0 but only answers on
 > interfaces it is configured to listen on.

1) This single line conf works, i.e. by default dnsmasq answers on all 
interfaces:
server=8.8.8.8

2) Adding no-resolv breaks the default behavior and makes dnsmasq answer 
only on lo:
no-resolv
server=8.8.8.8

3) But excluding a nonexistent interface makes it work again:
no-resolv
server=8.8.8.8
except-interface=nonexistent

This behavior makes no sense to me, that's why I reported it as a bug.
I believe at least (1) and (2) should have the same behavior.

In any case, if it's not considered a bug we don't need to waste any 
more time on it, as the (3) workaround is fine for anyone that needs it.

(I avoid bind-interfaces and bind-dynamic because they fail in certain 
scenarios, but that's another topic. I'll contribute bug reports on 
these some other time when I gather a small reproducible case like I did 
just now for no-resolv)

Thank you very much,
Alkis



More information about the Dnsmasq-discuss mailing list