Unbound Unbound on subnet router

[Zim]

I have two routers in my network - a main router and a subnet router. I have Unbound running successfully on the main router.

If I run Unbound on the subnet router, will there be any speed or performance benefits for the devices connected to the subnet router resulting from the Unbound cache on the subnet router?

My thinking is any device on the subnet that needs DNS resolution will access the Unbound cache on the subnet router first. If item is not in cache or is stale, then the subnet router will do recursive lookup to resolve the DNS. In theory, it should speed up things, right?


If so, how do I configure Unbound on the subnet router? I installed it on the subnet router, but it seems to be blocking all traffic.


Thanks in advance!

 

[dave14305]

I don’t imagine any advantage with Unbound on the subnet router over dnsmasq on the subnet router using the main router as its upstream server.

 

[Tech9]

In theory, it should speed up things, right?

The built-in dnsmasq is also caching DNS server. If you install Unbound for this - not needed.

 

[Zim]

Thanks @dave14305 and @Tech9 for this. Will stick to Unbound only on the main router.

 

[CornfieldWin]

I hope this thread is current even if the initial question was answered because it raises the second one. If not, I will create a new duplicate topic. With dnsmasq --> unbound --> internet on the main router, and dnsmasq on the secondary router --> dnsmasq on the main router, how does this handle the local domain(s) on the main router and secondary router so the two (actually multiple) dnsmasq instances can resolve local names on both routers (assuming router two is subnetted/Vlan)?

That's a nontrivial question to create a global DNS space locally that could involve either dnsmasq or unbound on the main router treating the dnsmasq on the second router as an upstream source, dnsmasq or unbound on the main router listening for dsnmasq on the second router as a requester, and dnsmasq on the second router listening for requests from whoever sends them from the main router. Ah, and make clever assignments that don't create circular loops. Are we looking at multiple dnsmasq configuration options or DNS record management in unbound to pull this off or both? Kinda like recursively scanning a tree structure in parallel without getting lost. I guess they don't call them recursive resolvers for no good reason. Would really like to know how to handle this.

 

[CornfieldWin]

The fog cleared. Moving to a new thread. Unbound was a distraction, it is never in the local domain resolution loop, just an upstream DNS server piped external DNS requests. The challenge is DNSMASQ main DNS server to DNSMASQ subnet server(s) which is not the same thing as a DNS subdomain server, this is not a mandatory hierarchical relationship!