On Wed, Jan 05, 2022 at 04:12:21PM +, Simon Kelley wrote:
>
> I did check it and it's a bit of a mess. Reverting efea282396 only
> coincidentally fixes the problem, knowing that it does made finding the
> real problem much easier, so thanks for that information.
>
> I believe the real fix is
Hi Simon,
commit efea282396 "Fix logic in add_update_server() to make
optimisation actually optimise." introduced a bug when re-reading
resolv.conf after changes. Found by git bisect and confirmed
by reverting efea282396 on top of current git 011f8cf1d011.
The issue happens when starting/stopping
On Thu, Nov 04, 2021 at 07:46:18AM +0100, Geert Stappers via Dnsmasq-discuss
wrote:
> On Wed, Nov 03, 2021 at 11:45:15PM +0100, Johannes Stezenbach wrote:
> >
> > I've tried current git version v2.87test4-2-g9560658c5ba2.
> >
> > Usually /run/dnsmasq/resol
Hi,
I've tried current git version v2.87test4-2-g9560658c5ba2.
Usually /run/dnsmasq/resolv.conf has only one entry for my
home Wifi router. When I enable a VPN connection two more
entries are added, but dnsmasq doesn't read it correctly.
Real:
nameserver 10.x.xx.60
nameserver 10.x.xx.75
nameserv
On Mon, Sep 27, 2021 at 10:45:25PM +0100, Simon Kelley wrote:
>
> I think that this is a 2.86 problem. There are two cases when dnsmasq
> will try another server with the same query:
>
> 1) When a client retries the query.
> 2) When the first server returns REFUSED.
>
> In the second case, it's
On Tue, Sep 21, 2021 at 09:40:17PM +0100, Simon Kelley wrote:
> On 21/09/2021 20:54, Johannes Stezenbach wrote:
> > This works the first time, but fails after dnsmasq is restarted:
> > dnsmasq: cannot open log /tmp/dnsmasq.log: Permission denied
> >
> > $ ls -l /tmp/d
Hi,
a minor issue I noticed while debugging:
I added this to the dnsmasq command line:
--log-queries=extra --log-debug --log-facility=/tmp/dnsmasq.log
(actually set in DNSMASQ_OPTS in /etc/default/dnsmasq in Debian)
This works the first time, but fails after dnsmasq is restarted:
dnsmasq: ca
On Tue, Sep 21, 2021 at 09:38:41AM +0100, Simon Kelley wrote:
> The culprit in --strict-order.
>
> Comment from the code to save my re-typing:
>
> /* In strict order mode, there must be a server later in the list
>left to send to, otherwise without the forwardall mechanism,
>code further
On Mon, Sep 20, 2021 at 11:16:09PM +0100, Simon Kelley wrote:
> On 20/09/2021 20:49, Johannes Stezenbach wrote:
> >
> > after recent update to 2.86 on Debian sid I'm seeing
> > failures in name resolution. I think the issue is that
> > my Wifi connection is current
Hi,
after recent update to 2.86 on Debian sid I'm seeing
failures in name resolution. I think the issue is that
my Wifi connection is currently flaky (another problem
to solve...) and the DNS reply gets lost. After that
dnsmasq reports REFUSED, e.g.:
Sep 20 21:06:38 dnsmasq[18805]: 55 127.0.0.1/3
10 matches
Mail list logo
