Home
Help
Search
Login
Register
OPNsense Forum
»
English Forums
»
24.1 Legacy Series
»
Different upstream DNS forwarder depending on source
« previous
next »
Print
Pages: [
1
]
Author
Topic: Different upstream DNS forwarder depending on source (Read 506 times)
andre.lackmann
Newbie
Posts: 5
Karma: 0
Different upstream DNS forwarder depending on source
«
on:
May 05, 2024, 04:48:11 am »
I have a few network segments in my home network. I want to be able to use NextDNS filtering for my IOT network that I also use to block specific applications when the kids use the wifi.
I currently can achieve this using the NextDNS command line tool in a docker container. I'm just forwarding all DNS requests from that segment to the docker container on another host. I'd prefer to not use this extra service though as it's just another thing to manage.
Is there any way to configure Unbound to use a different upstream DNS server depending on the source net/IP of the request? If not, is there any other way to have OPNSense achieve the same? Appreciate any suggestions
Logged
zan
Full Member
Posts: 175
Karma: 31
Re: Different upstream DNS forwarder depending on source
«
Reply #1 on:
May 05, 2024, 05:28:34 am »
Unbound doesn't support it.
You may consider using AdGuardHome plugin, it has support for selective upstream for different sources under its Settings>Client settings.
Logged
andre.lackmann
Newbie
Posts: 5
Karma: 0
Re: Different upstream DNS forwarder depending on source
«
Reply #2 on:
May 06, 2024, 01:11:25 am »
I'd rather not switch to AdGuardHome. Is it feasible to use dnsmasq on a different port, port forwarded from that network segment? If Unbound doesn't have the functionality, seems the only other way. But not sure if dnsmasq can do DNS over TLS and have a different upstream from the rest of the gateway. Has anyone done this?
Logged
Print
Pages: [
1
]
« previous
next »
OPNsense Forum
»
English Forums
»
24.1 Legacy Series
»
Different upstream DNS forwarder depending on source