• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Unbound not resolving using default 127.0.0.1

Scheduled Pinned Locked Moved DHCP and DNS
4 Posts 2 Posters 408 Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • C
    cdelrey
    last edited by Jun 12, 2023, 3:04 PM

    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

    T C 2 Replies Last reply Jun 12, 2023, 5:06 PM Reply Quote 0
    • T
      the other @cdelrey
      last edited by Jun 12, 2023, 5:06 PM

      @cdelrey hey there,
      is there by chance an entry under
      System > General Settings > DNS Server
      ??

      the other

      pure amateur home user, no business or professional background
      please excuse poor english skills and typpoz :)

      1 Reply Last reply Reply Quote 0
      • C
        cdelrey @cdelrey
        last edited by Jun 12, 2023, 6:26 PM

        @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.

        Selection_127.png

        Wanted to get some insights before I made this change

        1 Reply Last reply Reply Quote 0
        • C
          cdelrey
          last edited by Jun 13, 2023, 1:20 PM

          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

          1 Reply Last reply Reply Quote 0
          4 out of 4
          • First post
            4/4
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
            This community forum collects and processes your personal information.
            consent.not_received