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

    removing 127.0.0.1 from DNS search order

    Scheduled Pinned Locked Moved DHCP and DNS
    4 Posts 3 Posters 299 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.
    • E
      Ellis Michael Lieberman
      last edited by

      Here is what the current DNS server search order looks like.
      alt text

      Now, the LAN two based name-servers support the LAN based mail server as well as other loval servers. They are NOT the publicly available servers, though other than the local domain they get all the resolution from the net. So mail.netwright,net, resolves locally to 192.168.1.78 but publicly to via a public record it resolves to 58.69.150.45. My LAN based PC's have no problem resolving this as they are only resolving against the private nameservers, but cellphones when using local WiFi appear to run into problems with resolution, I am not sure, but it is possible that the reason might be that the Netgate appliance has the public address.

      That is the reason I would like to remove 127.0.0.1 from the OS DNS resolution. Can I do this? The GUI doesn't seem to have a way. to accomplish this. If I SSH into the unit, can I change the value there?

      V 1 Reply Last reply Reply Quote 0
      • V
        viragomann @Ellis Michael Lieberman
        last edited by

        @Ellis-Michael-Lieberman
        The shown servers are used by pfSense only.
        The point is, which servers your devices request to resolve host names.

        If pfSense is your DHCP server enter your local DNS servers in the DHCP settings of each enabled interface to hand them out to the clients.

        If the mobile devices don't respect this for whatever reason, you can workaround this by port forwarding all DHCP requests to any other server than the local to one of your local servers.

        However, my suspicion is, that the devices requests DoH servers in fact.
        This could be prohibited by proper pfBlockerNG rules.

        S 1 Reply Last reply Reply Quote 0
        • S
          SteveITS Galactic Empire @viragomann
          last edited by

          @viragomann said in removing 127.0.0.1 from DNS search order:

          If the mobile devices don't respect this for whatever reason, you can workaround this by port forwarding all DHCP requests to any other server than the local to one of your local servers.

          …think you meant “DNS requests” here…

          @Ellis-Michael-Lieberman if devices need to use pfSense for DNS you can use a host override or domain override. Remember IPv6 too, if enabled.

          Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
          When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
          Upvote 👍 helpful posts!

          V 1 Reply Last reply Reply Quote 0
          • V
            viragomann @SteveITS
            last edited by

            @SteveITS said in removing 127.0.0.1 from DNS search order:

            …think you meant “DNS requests” here…

            Yes, of course DNS.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.