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

    Unbound resolver stop working in 2.3

    Scheduled Pinned Locked Moved DHCP and DNS
    5 Posts 3 Posters 1.4k 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 Offline
      cjbujold
      last edited by

      In version 2.3 by resolver just stopped working when I try to start it it has a fatal crash when I try to save the setting again I get the following.  How can I fix?

      The generated config file cannot be parsed by unbound. Please correct the following errors:
          [1461185314] unbound-checkconf[21542:0] error: cannot parse netblock: '/'
          [1461185314] unbound-checkconf[21542:0] fatal error: cannot parse access control address / allow

      Apr 20 17:51:36 unbound 33288:0 fatal error: Could not setup access control list
      Apr 20 17:51:36 unbound 33288:0 error: cannot parse access control: / allow
      Apr 20 17:51:36 unbound 33288:0 error: cannot parse netblock: '/'

      1 Reply Last reply Reply Quote 0
      • A Offline
        azekiel
        last edited by

        Clear out Services: DNS Resolver : Access Lists for testing and see if it works then.

        This was a old problem which was already fixed. You sure it's 2.3?

        https://redmine.pfsense.org/issues/4046

        1 Reply Last reply Reply Quote 0
        • C Offline
          cjbujold
          last edited by

          version Info:

          2.3-RELEASE (amd64)
          built on Mon Apr 11 18:10:34 CDT 2016
          FreeBSD 10.3-RELEASE

          Cleared access list and recreated and issue when away.

          Thanks

          1 Reply Last reply Reply Quote 0
          • A Offline
            azekiel
            last edited by

            Please open up a ticket with more detailed information (What was in Access Lists an so on) so this problem can be fixed?

            1 Reply Last reply Reply Quote 0
            • C Offline
              cmb
              last edited by

              If you can show the changes from your config history, I can see how that might have been possible. Diag>Backup/restore, Config history tab. Choose the left radio button from the last config revision that didn't work, the right radio button on the first config revision where it was fixed, and hit "diff". Paste that output. Can PM it to me if there's something there you're not comfortable posting publicly.

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