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

    After upgrading to 2.4.0-BETA DNS Resolver generates errors

    Scheduled Pinned Locked Moved 2.4 Development Snapshots
    6 Posts 3 Posters 1.3k 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.
    • M
      MrMonk
      last edited by

      Just upgraded to 2.4.0-BETA, and DNS Resolver is generating the following errors:

      "The following input errors were detected:
      The generated config file cannot be parsed by unbound. Please correct the following errors:
      /var/unbound/test/root.key: No such file or directory
      [1488084729] unbound-checkconf[95265:0] fatal error: auto-trust-anchor-file: "/var/unbound/test/root.key" does not exist in chrootdir /var/unbound"

      Prior to the upgrade, I did not get these errors.

      Any suggestions?

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

        I was able to get it working by creating the test directory and copying over the following files:

        root.key
        unbound.conf
        unbound_control.key
        unbound_control.pem
        unbound_server.key
        unbound_server.pem

        Is there a permanent fix for this?  Not sure what the next steps should be.

        1 Reply Last reply Reply Quote 0
        • jimpJ
          jimp Rebel Alliance Developer Netgate
          last edited by

          I'm not seeing that on any of mine.

          What were you running before?

          Are you using /tmp and /var in RAM disks?

          Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

          Need help fast? Netgate Global Support!

          Do not Chat/PM for help!

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

            This was already reported by someone on 2.3.x and ended up with a reinstall, AFAICT. It just doesn't make sense. https://forum.pfsense.org/index.php?topic=118226.0

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

              Thannks for the links and questions.  I'm new to pfsense, so i'm still figuring stuff out.

              The link looks like a similar situation.  Upgraded to larest release today and it seems to have fixed the error messages.  Is it possible to test that the resolver is caching?

              My thanks in advance.

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

                Forgot to provide the release.  Upgraded to 2.4.0-BETA (arm) built on Sun Feb 26 21:23:35 CST 2017 FreeBSD 11.0-RELEASE-p8

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