Hi Team,
We are facing a dnsmasq crash on version 2.81. We are not aware of steps to
trigger the crash, but we used to get this crash frequently.
Crash Details:
Thread 0 (crashed)
0 dnsmasq!check_dns_listeners [dnsmasq.c : 1768 + 0x0]
r0 = 0xr1 = 0x0009r2 = 0x0009
Hi,
"How To Ask Questions The Smart Way" has immediately after the introduction
an advice on before you ask.
http://www.catb.org/esr/faqs/smart-questions.html#before
Following that advice is still no guarantee for a quick response.
So when you are still stuck with something that you think
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
On 02.03.22 19:24, Simon Kelley wrote:
The behaviour on this alternated between what you observed and what
you advocate a few times before settling.
The problem with waiting for all replies is that a common source of
SERVFAIL returns is domains with broken DNSSEC. In that case all the
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
On Sun, Mar 06, 2022 at 07:22:19AM +0200, Alkis Georgopoulos wrote:
> On 3/6/22 05:35, Donald Muller wrote:
> > Alkis Georgopoulos
> > Sent Saturday, March 5, 2022 4:46 PM
> > >
> > > Hi, on Ubuntu 22.04 and dnsmasq 2.86-1.1:
> > >
> > > 1) Use the following dnsmasq.conf:
> > > no-resolv
>
