Closed mernamer closed 1 year ago
I fixed it!
Best guess: I changed the LAN DNS server to something other than the router for some reason, I updated it to blank (which sends it to the router). I changed it originally because I misunderstood the purpose of it on the LAN tab.
Explanation: LAN DNS server is for DHCP assignments, sending it anywhere other than the router (or your local DNS server, if you've moved it to another device for some reason), makes sense changing to something else would mess up a custom domain to a local address.
Also added to the conf, don't think this was the fix:
private-domain: my.domain.org
Also, did some digging on the many places you can update the DNS server:
Could make so don't need to activate DNS Filter, but would lose ability to filter which devices use Unbound from the web interface, i.e., sometimes apps on smart TVs / Roku don't like custom DNS. There are other ways to route those devices, would just add some steps.
If adventures in avoiding DNS Filter is worthy of documentation, can update.
What I expected to happen: Custom domain would direct to correct local IP when using domain on local network.
What I did: Updated unbound.conf with custom domains after...
Then set up domains in unbound.conf as such, without comments:
Domain names and IPs are changed to protect the innocent or whatever.
Updated the conf in the manager, confirmed it's still running, even tried a reboot.
What happened instead: It just didn't work.
Additional details / logs Cursory review of /var/logs showed nothing useful
? menu (running v3.22):
Looks to be running:
unbound (pid #####) is running...
Statistics menu:Can provide other logs upon request.
This tool is great, regardless of this issue I probably caused and big thanks for making it available. I've scoured some volume of available docs, worried I missed something obvious, apologies if that's the case.
ETA: Just tweaked formatting for readablity.