Unbound not resolving using default 127.0.0.1
-
I have DNS over TLS configured which works fine. I also have the default setting to use Local DNS, fall back to Remote DNS (Default). What I noticed is local DNS fail to resolve from the system itself from the UI or the CLI fail. From the CLI I have to explicitly call localhost to resolve "host local.domain 127.0.0.1" or "dig local.domain @127.0.0.1"
What's interesting is the resolv.conf file matches the unbound.conf file for the DNS forward statements.
Is this duplicative? shouldn't resolv.conf point to 127.0.0.1 for unbound to then forward to the upstream?
Thanks, Chris
-
@cdelrey hey there,
is there by chance an entry under
System > General Settings > DNS Server
?? -
@cdelrey yes, per the guide for DNS over TLS I have cloudfare dns servers. I want to try setting this to 127.0.0.1 instead. I have both unbound (listening on 127.0.0.1:54, and BIND listening on my local interfaces listening on port 53.
Wanted to get some insights before I made this change
-
So I updated the resolv.conf file and everything is resolving correct now. But I don't see anything reflecting differently in the UI. So my question, is there a way to persist unique settings in resolv.conf for local DNS to point to local, 127.0.0.1 from unbound forward listed IPs? Once I made this change above, I updated to the latest version, rebooted and my changes are not gone, resolv.conf matches the same forward IPs stated in the UI (screenshot) and in unbound.conf
Thanks
