Unbound Interface Forwarding
-
How do I do this in Unbound Custom options:
server:
do-not-query-localhost: no
forward-zone:Interface: 10.0.1.1 Name: "." forward-addr: 10.0.1.1@53 Interface: 10.0.1.10 Name: "." forward-addr: 10.0.1.101@53 Interface: 10.0.1.20 Name: "." forward-addr: 10.0.1.20@53 Interface: 10.0.1.30 Name: "." forward-addr: 10.0.1.30@53Is this the proper syntax?
-
What is the goal? What exactly are you trying to accomplish?
Why would you have so many IPs on the same network?
-
As always, thanks for the reply.
My primary goal here is to have DNS gateway for every interface for easy monitoring of clients. Every interface represent a segregated subnet. And every device has a "description" attached to it when they make a query for even easier identification. This is done through Adguard Home UI using NextDNS. I welcome tweaks and tricks if you have any.
Hence, I am now conducting this experiment. I thought maybe Unbound will be more efficient if it does the forwarding it self rather than using port forwarding.
As always, I welcome your thoughts
-
@magikmark huh, unbound out of the box would listen on any interface you have. And then you can pick if you want interfaces it listens on if you want to leave some off.
But your examples would all be on the same interface unless you were using like really tiny masks. And then those numbers would still be odd because they are not the first IP in the block, etc.
So if you have 10.0.1/24 and a 10.0.2/24 unbound out of the box would listen on those interfaces.
As to forwarding, sure you can setup unbound to forward, you don't need to use option box for that. So not sure where the port forwarding is coming from, the only time you would want to do port forwarding for dns, is if you wanted to intercept traffic to some other dns like if the client was trying to ask 8.8.8.8 and you wanted it direct that to unbound and it was forwarding to say 9.9.9.9 or was just resolving, etc.
example, vs using all - you can select what interfaces you want unbound to listen on