Hey Rick,
On 9/24/2021 4:05, Rick Thomas wrote:
You are right. It is a mis-config. If you have the time and interest, I'd
appreciate any help you (or the list) can give on correcting the mis-config...
Here's the story:
As noted, my ISP does not provide IPv6 and has no plans to provide it
You are right. It is a mis-config. If you have the time and interest, I'd
appreciate any help you (or the list) can give on correcting the mis-config...
Here's the story:
As noted, my ISP does not provide IPv6 and has no plans to provide it in the
future. I've emailed their technical help
On 23/09/2021 18:16, Petr Menšík wrote:
> I am quite sure also --rebind-domain-ok is broken. It allocates struct
> serv_local, but does not set any flags if I saw it correctly. Therefore
> it would be later threated as struct server and checked in wrong places.
Those structures are kept on a
On Thu, 2021-09-23 at 11:00 +0100, Simon Kelley wrote:
> I just pushed a pretty straightforward patch to fix this.
Can confirm this fixes it.
Best,
Dominik
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
Hi Michael,
It works, i've created a docker-compose project with two dnsmasq
instance, each one listening on one ethernet alias. I've disabled dchp
on the children instance.
Thanks for the advice!
Hubert.
Le 23/09/2021 à 18:43, Michael a écrit :
On 9/23/21 04:35, Petr Menšík wrote:
Hi
On 23/09/2021 17:43, Michael wrote:
> On 9/23/21 04:35, Petr Menšík wrote:
>> Hi Hubert,
>>
>> it may work, if you would run two dnsmasq instances. One for children
>> with OpenDNS as upstream servers, another for everyone else.
>>
>> default instance:
>>
>> bind-interfaces
>>
I am quite sure also --rebind-domain-ok is broken. It allocates struct
serv_local, but does not set any flags if I saw it correctly. Therefore
it would be later threated as struct server and checked in wrong places.
That is still unfixed even after commit
de372d6914ae20a1f9997815f258efbf3b14c39b.
On 9/23/21 04:35, Petr Menšík wrote:
Hi Hubert,
it may work, if you would run two dnsmasq instances. One for children
with OpenDNS as upstream servers, another for everyone else.
default instance:
bind-interfaces
listen-address=10.1.0.1
server=8.8.8.8
domain=home.arpa
Hi Simon,
Thank you for the patch, and the explanation.
Best,
Jean-Philippe
Le 23/09/2021 à 12:00, Simon Kelley a écrit :
Apologies all.
The
--address=/#/..
functionality got omitted in the 2.86 domain-search rewrite, which
explains everything. Treating # as a domain name, it doesn't
Hi Hubert,
it may work, if you would run two dnsmasq instances. One for children
with OpenDNS as upstream servers, another for everyone else.
default instance:
bind-interfaces
listen-address=10.1.0.1
server=8.8.8.8
domain=home.arpa
dhcp-option=option:dns-server,10.1.0.1,8.8.8.8
On 22/09/2021 23:07, Petr Menšík wrote:
> Good catch. A new bug #2006367 [1] were also reported on Fedora. It
> seems to point to related structures and memory corruption in them. I
> have no coredump to check it (yet), so mostly guessing.
>
> Juggling with type unsafe structures with few
Apologies all.
The
--address=/#/..
functionality got omitted in the 2.86 domain-search rewrite, which
explains everything. Treating # as a domain name, it doesn't match the
test domain, so dnsmasq tries to forward upstream. There are no upstream
servers configured, so it returns REFUSED.
I
Applied. Thanks.
Cheers,
Simon.
On 22/09/2021 14:36, Dominik Derigs wrote:
> When users specify a file (instead of a directory) as argument of
> hostsdir, dnsmasq will log:
>
>> dnsmasq: bad dynamic directory hosts: Success
>
> because stat() didn't fail for this file, however, the test
>
My ISP does not support IPv6 at all. Recently I have been having trouble
connecting (web and/or ssh) to hosts outside of my local home LAN that have
both IPv4 and IPv6 addresses.
For example:
rbthomas@monk:~$ host www.google.com
www.google.com has address 142.251.33.68
14 matches
Mail list logo
