On 17.02.21, 23:48, "Simon Kelley" wrote:
> > When submitting a patch I noticed that the Dnsmasq mailing list modifies
> > the subject of the email (prefix [Dnsmasq-discuss]) as well as appends
> > 'Dnsmasq-discuss mailing list' information to the end of my message.
>
> There's no particular
On 17.02.21, 23:41, "Dnsmasq-discuss on behalf of Geert Stappers"
wrote:
> > @@ -567,6 +568,12 @@ struct ipsets {
> >struct ipsets *next;
> > };
> >
> > +struct allowlist {
> > + uint32_t mark, mask;
> > + char **patterns;
> > + struct allowlist *next;
> > +};
> > +
>
> I think the
On Wed, Feb 17, 2021 at 4:36 PM Simon Kelley wrote:
>
> On 09/02/2021 04:08, Amit wrote:
> > On Wed, Feb 3, 2021 at 12:16 PM Geert Stappers wrote:
> >>
> >
> > [snip]
> >
> >>
> >> My guess:
> >>
> >> } } Where is the `ping www.google.com` done?
> >> } The ping is done at the end of the chain
>
On 09/02/2021 04:08, Amit wrote:
> On Wed, Feb 3, 2021 at 12:16 PM Geert Stappers wrote:
>>
>
> [snip]
>
>>
>> My guess:
>>
>> } } Where is the `ping www.google.com` done?
>> } The ping is done at the end of the chain
>> } } Where and how is IPv6 disabled?
>> } Same machine, magic from Network
On 16/02/2021 00:42, Nicholas Mu wrote:
> Hi,
>
> I noticed a low level increase in DNS errors after upgrading to 2.84.
> After doing some packet diving, it seems that retries behave differently
> in the new version. For my testing, I'm using dnspython but I believe
> this issue would affect any
On 17/02/2021 13:54, Etan Kissling wrote:
> When submitting a patch I noticed that the Dnsmasq mailing list modifies
> the subject of the email (prefix [Dnsmasq-discuss]) as well as appends
> 'Dnsmasq-discuss mailing list' information to the end of my message.
>
> These modifications break DKIM
On Wed, Feb 17, 2021 at 02:54:46PM +0100, Etan Kissling wrote:
> When submitting a patch I noticed that the Dnsmasq mailing list modifies
> the subject of the email (prefix [Dnsmasq-discuss]) as well as appends
> 'Dnsmasq-discuss mailing list' information to the end of my message.
>
> These
Hello people,
I've got a strange issue with a high traffic (>5 requests / sec) where it
sometimes does not responde with the NXDOMAIN but with NOERROR.
When we ask the upstream DNS directly we always get a NXDOMAIN response.
We use DNSmasq 2.80-1.1ubuntu1.2
We worked around this issue by
When submitting a patch I noticed that the Dnsmasq mailing list modifies
the subject of the email (prefix [Dnsmasq-discuss]) as well as appends
'Dnsmasq-discuss mailing list' information to the end of my message.
These modifications break DKIM signatures of our emails, leading to them
being
