On 7/17/25 19:53, [email protected] wrote:
Dear dnsmasq people,
This is not a problem with dnsmasq itself, but I don't know where else
to ask, so I am going ahead and I apologise in advance of it's off-topic.
I have been using dnsmasq for months with various clients and had no
trouble at all, until I tried a Debian client. The problem I have is
that the client attaches to two networks automatically: a wired one
which is connected to my dnsmasq server, and a wifi connection to a
router which is on another private subnet which is NOT routed by my
server. But when both interfaces are up the client tries to use the
wrong DNS server. It's the wrong one because it's not on the subnet my
server is routing. If only one of either of the Debian client's
interfaces is up it works fine.
So, is there anything I could potentially do in the dnsmasq
configuration to stop this behaviour? Is it even the right behaviour?
Maybe I should try raise it as a bug against Debian, but I am not sure
about this.
Apologies again if this is off-topic, just ignore it and be thankful
that I didn't put my questions in a zip file! :-)
The source of the problem is the wifi router. Can you change its
configuration so that it doesn't advertise a DNS server which doesn't work?
Cheers,
Simon.
Ian
_______________________________________________
Dnsmasq-discuss mailing list
[email protected]
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
_______________________________________________
Dnsmasq-discuss mailing list
[email protected]
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
