Thank you for dnsmasq. I'm just happy I was able to come up with a
fairly simple way to reproduce the bug.
I applied the change in commit 930428fb970 as a patch to dnsmasq 2.87,
and that fixes the problem for me as well.
Thanks again for all your hard work.
On 10/17/22 15:26, Simon Kelley
All of the examples I see for setting up dnsmasq on networks without a
"real" domain always say to choose a "fake" local domain (e.g. .lan,
..home.arpa, .local, etc.). Then you also configure dnsmask to treat
that domain as local so that requests for that domain are never
forwarded.
Why?
Are you
On 2022-10-18, Grant Edwards wrote:
> Are you not allowed to have have an empty domain so that "plain"
> hostnames are satisfied locall (e.g. from /etc/hosts and the DHCP
> leases) and only requests with a domain are forwarded to the external
> server?
Are there DHCP clients that fall over if
On 16.10.22 23:25, Christopher J. Madsen wrote:
> I tried building dnsmasq 2.87 with a patch that reverts commit 553c4c99,
> and that does seem to fix the problem.
Related to the very same patch, but from a slightly different angle:
automatic reload of $resolv-file purges all upstream servers
Thank you very much for the information below. Having that saved me a
load of time.
The problem, as ever, is linked lists and
https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=930428fb970f4991e5c2933fd5a5d2504c18a551
fixes things for me.
To preempt the next question, I intend to
On Mon, Oct 17, 2022 at 09:26:39PM +0100, Simon Kelley wrote:
Subject: Re: [Dnsmasq-discuss] Problem with dynamic upstream nameservers in
dnsmasq 2.87
In-Reply-To: <13bd0bd5-3cd9-cb5c-a7a4-955c0ebe1...@thekelleys.org.uk>
> Thank you very much for the information below. Having that saved me a
