> On 5 Jul 2021, at 21:12, Simon Kelley wrote:
>
> On 05/07/2021 19:31, Kevin Darbyshire-Bryant wrote:
>>
>>
>>> On 5 Jul 2021, at 16:53, Dominik DL6ER wrote:
>>>
>>> Hey Simon,
>>>
>>> the current dnsmasq master version contains a bug rewriting all
>>> NXDOMAIN replies from upstream with
On 05/07/2021 16:53, Dominik DL6ER wrote:
> Hey Simon,
>
> the current dnsmasq master version contains a bug rewriting all
> NXDOMAIN replies from upstream with NOERROR.
>
> The error has been introduced in commit
> d0ae3f5a4dc094e8fe2a3c607028c1c59f42f473 (see attached diff) and is
> ultimately
On 05/07/2021 12:34, Rockwell, Dennis wrote:
> I have a situation for which extending those features would be the exact
> solution.
>
The code is there at the bleeding edge now.
https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=5bcca1219af8bad328352d7a656bc9b1e9d61b92
Simon.
>
On 05/07/2021 09:20, Kevin Darbyshire-Bryant wrote:
>
>> I looked at the code that determines private addresses for --bogus-priv
>> and rebind: It's a bit unruly for IPv6, so I've rationalised things and
>> included :: and 0.0.0.0 in the --rebind-localhost-ok coverage, which at
>> least avoids
On 05/07/2021 12:49, Petr Menšík wrote:
> Hi,
>
> more below.
>
> On 7/2/21 6:18 PM, Simon Kelley wrote:
>> On 02/07/2021 15:42, Petr Menšík wrote:
>>> Hi,
>>>
>>> current dnsmasq has a bug [1] in handling hostname setting. When two
>>> hosts request equal hostname, dnsmasq will reset name in
On 05/07/2021 19:31, Kevin Darbyshire-Bryant wrote:
>
>
>> On 5 Jul 2021, at 16:53, Dominik DL6ER wrote:
>>
>> Hey Simon,
>>
>> the current dnsmasq master version contains a bug rewriting all
>> NXDOMAIN replies from upstream with NOERROR.
>>
>> The error has been introduced in commit
>>
> On 5 Jul 2021, at 16:53, Dominik DL6ER wrote:
>
> Hey Simon,
>
> the current dnsmasq master version contains a bug rewriting all
> NXDOMAIN replies from upstream with NOERROR.
>
> The error has been introduced in commit
> d0ae3f5a4dc094e8fe2a3c607028c1c59f42f473 (see attached diff) and is
Hey Simon,
the current dnsmasq master version contains a bug rewriting all
NXDOMAIN replies from upstream with NOERROR.
The error has been introduced in commit
d0ae3f5a4dc094e8fe2a3c607028c1c59f42f473 (see attached diff) and is
ultimately caused by
> lookup_domain(daemon->namebuff, F_CONFIG,
Hi,
more below.
On 7/2/21 6:18 PM, Simon Kelley wrote:
> On 02/07/2021 15:42, Petr Menšík wrote:
>> Hi,
>>
>> current dnsmasq has a bug [1] in handling hostname setting. When two
>> hosts request equal hostname, dnsmasq will reset name in previous lease
>> and change registered name to the most
I have a situation for which extending those features would be the exact
solution.
Dennis
On Jul 4, 2021 5:21 PM, Simon Kelley wrote:
On 04/07/2021 21:32, Simon Kelley wrote:
> On 30/06/2021 10:40, Kevin Darbyshire-Bryant wrote:
>> As an ‘experiment’ I tried switching from my own local
10 matches
Mail list logo
