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
--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 use 1.1.1.3.
Thanks,
jonathan
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 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
> > >
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
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
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,
