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

    DNS Forwarder not working on reboot

    Scheduled Pinned Locked Moved General pfSense Questions
    3 Posts 3 Posters 533 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.
    • R
      rquigley
      last edited by

      Hi All,

      I'm currently using the DNS Forwarder as a means of serving internal DNS for services I run on my network.

      For some reason, I'm noticing that any time I restart or boot cold my instance, the internal DNS doesn't resolve. I'm able to fix this by simply saving the existing configuration in the GUI and Apply Changes which gets it up and running again.

      I'm just wanting to know whether this is an issue for all or just myself?

      I'm running PfSense 2.4.2-RELEASE-P1.

      Any assistance would be appreciated. Many thanks!

      1 Reply Last reply Reply Quote 0
      • F
        fcapizzo
        last edited by

        I reported this (https://forum.pfsense.org/index.php?topic=132179.msg727024) back in 2017, but no one replied.  This still happens to me now.

        The most annoying instance of this happening is I update pfSense by connecting internal DNS entry for my pfSense router.  The last part of the update reboots the router and waits for it to be reachable afterwards.  Unfortunately, because DNS Forwarder does not work correctly on reboot, it looks as if the update fails.  At that time I need to connect to the router via IP, and then restart DNS Forwarder.

        I wish this was fixed, because this is really the only issue I have with pfSense.

        1 Reply Last reply Reply Quote 0
        • M
          marvosa
          last edited by

          Several upgrades ago, I had a similar issue with the forwarder… where it would not resolve anything after an upgrade.    I never tried re-saving the config, but what did work for me was specifically selecting my LAN interfaces on Services -> DNS Forwarder instead of leaving it on "All".

          We may have two totally separate issues, but it's worth a shot.

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