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

    PfSense DNS Won't Resolve - failed to access /etc/resolv.conf

    Scheduled Pinned Locked Moved DHCP and DNS
    5 Posts 2 Posters 2.0k 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
      ericb0813
      last edited by

      I have been having some issue with DNS on my 2.1.5 Nano install.  In General Setup I have added 3 dns servers, however under the dashboard in system information, dns servers field is blank and Pfsense can not resolve anything.    I look at the system logs under resolver and these errors appeared (See Below) .  I tried to edit this file and it says the file does not exist but if I go into the shell and look there is a file with that name however I cant open it in any text editor.  Any idea guys?

      Apr 27 14:13:32	dnsmasq[59378]: started, version 2.70 cachesize 10000
      Apr 27 14:13:32	dnsmasq[59378]: compile time options: IPv6 GNU-getopt no-DBus i18n IDN DHCP DHCPv6 no-Lua TFTP no-conntrack no-ipset auth DNSSEC
      Apr 27 14:13:32	dnsmasq[59378]: failed to access /etc/resolv.conf: No such file or directory
      Apr 27 14:13:32	dnsmasq[59378]: read /etc/hosts - 2 addresses
      ```![Capture.PNG](/public/_imported_attachments_/1/Capture.PNG)
      ![Capture.PNG_thumb](/public/_imported_attachments_/1/Capture.PNG_thumb)
      1 Reply Last reply Reply Quote 0
      • E
        ericb0813
        last edited by

        So I deleted the existing resolv.conf (It was empty) and created it again then added my nameservers and everything seems to be working except I have to edit it manually for some reason instead of it getting updated by the GUI.  Also the DNS servers section in system information is still blank.

        1 Reply Last reply Reply Quote 0
        • D
          doktornotor Banned
          last edited by

          Why don't you reinstall your obviously screwed box and restore the config?

          1 Reply Last reply Reply Quote 0
          • E
            ericb0813
            last edited by

            Yeah its got to be something like that.  I had it installed with no issues last night and on the firebox there is some glitches that required re-installing to resolve.  After a clean re-install this issue started.  I'm going to leave it for now since I don't change dns very often, and after a reboot the correct dns server were listed in the system information so I just have to update that resolv.conf file manually and it seems to work.

            1 Reply Last reply Reply Quote 0
            • D
              doktornotor Banned
              last edited by

              Well, you either have screwed permissions on the box, or screwed filesystem, or possibly both. There's no way I'd continue running a system with such unexplicable issues when it takes minutes to re-image and get a sane install.

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