On Sat, Dec 31, 2022 at 11:28 AM Geert Stappers
wrote:
> On Thu, Dec 29, 2022 at 05:34:24PM -0500, Jonathan Stafford wrote:
> > On Thu, Dec 22, 2022 at 3:46 PM Michael Smith
> wrote:
> >
> > > I run 2 instances of pihole (DNSmasq) on docker. Each run on their
> own
> > > IP address (macvlan)
On Thu, Dec 29, 2022 at 05:34:24PM -0500, Jonathan Stafford wrote:
> On Thu, Dec 22, 2022 at 3:46 PM Michael Smith wrote:
>
> > I run 2 instances of pihole (DNSmasq) on docker. Each run on their own
> > IP address (macvlan) separate from the docker host. Their IP addresses
> > are .2 and .3.
On Thu, Dec 22, 2022 at 3:46 PM Michael Smith wrote:
> I run 2 instances of pihole (DNSmasq) on docker. Each run on their own
> IP address (macvlan) separate from the docker host. Their IP addresses
> are .2 and .3.
>
>
> The .2 host is primary and forwards upstream to 1.1.1.1. This
On 12/18/22 09:10, Jonathan Stafford wrote:
Thanks, Michael. That will work to get them using that server, but
it's totally bypassing dnsmasq which means my local entries from
/etc/hosts don't resolve. I'd like both things to work to be difficult :)
Hi Jonathan,
Sorry, I didn't respond
: maandag 19 december 2022 18:09
Aan: egc6...@gmail.com
CC: Michael Smith ; Jonathan Stafford
; dnsmasq-discuss@lists.thekelleys.org.uk
Onderwerp: Re: [Dnsmasq-discuss] Change upstream server by client?
Thank you, I had not realized that 'use-applications-dns.net
<http://use-applications-dns.
zondag 18 december 2022 19:44
> *Aan:* Michael Smith
> *CC:* Jonathan Stafford ;
> dnsmasq-discuss@lists.thekelleys.org.uk
> *Onderwerp:* Re: [Dnsmasq-discuss] Change upstream server by client?
>
>
>
> Well, the real issue is DNS "leakage", because some (most?) bro
: Michael Smith
CC: Jonathan Stafford ;
dnsmasq-discuss@lists.thekelleys.org.uk
Onderwerp: Re: [Dnsmasq-discuss] Change upstream server by client?
Well, the real issue is DNS "leakage", because some (most?) browsers and lots
of phone apps use their own resolvers, thus bypassing your adve
Well, the real issue is DNS "leakage", because some (most?) browsers and
lots of phone apps use their own resolvers, thus bypassing your advertised
DNS resolver. My solution is on the router: I set up dnsmasq as my local
resolver (with adblock and DNSSEC, stubby is my backend for DoT), don't
even
On Sun, Dec 18, 2022 at 06:12:33PM +0100, Geert Stappers via Dnsmasq-discuss
wrote:
> On Sun, Dec 18, 2022 at 11:10:21AM -0500, Jonathan Stafford wrote:
> > On Sun, Dec 18, 2022 at 10:36 AM Michael Smith wrote:
> > > On 12/18/22 06:59, Jonathan Stafford wrote:
> > > > prequel, completely made
I am not aware of a way, but hopefully someone else has ideas. I run two instances of pihole. One for the grown ups that points upstream to 1.1.1.1 and the other points to 1.1.1.3. Then I use similar stanzas below to point the clients to the right piholeMichael On Dec 18, 2022, at 9:10 AM,
On Sun, Dec 18, 2022 at 11:10:21AM -0500, Jonathan Stafford wrote:
>
> On Sun, Dec 18, 2022 at 10:36 AM Michael Smith wrote:
>
> > On 12/18/22 06:59, Jonathan Stafford wrote:
> >
> > > prequel, completely made up:
> > > >
> > > > LAN is 192.168.6.0/24
> > > > Dnsmasq is at 192.168.6.10
> > >
Thanks, Michael. That will work to get them using that server, but it's
totally bypassing dnsmasq which means my local entries from /etc/hosts
don't resolve. I'd like both things to work to be difficult :)
On Sun, Dec 18, 2022 at 10:36 AM Michael Smith wrote:
> On 12/18/22 06:59, Jonathan
On 12/18/22 06:59, Jonathan Stafford wrote:
--server provides a way to change upstream resolvers based on the
domain being queried. Is there a way to make the same sort of change
based on the client doing the querying? For example, I'd like the IP
address range I use for my kids' devices to
13 matches
Mail list logo
