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

    DNS Resolver / General settings | Unable to save changes

    Scheduled Pinned Locked Moved DHCP and DNS
    7 Posts 4 Posters 1.0k Views 4 Watching
    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.
    • I Offline
      ic_attila
      last edited by rcoleman-netgate

      Re: DNS Resolver (unbound) / Can't change config

      Hello!

      I have a similar issue described on this topic.

      I have a recently upgraded pfSense Plus 22.05.

      After the upgrade, I noticed that the unbound (DNS Resolver) service is not running. I've tried all the workarounds I found in the forum, without success. I still getting the following error, if I try to save the config.

      The following input errors were detected:
      
          The generated config file cannot be parsed by unbound. Please correct the following errors:
          /var/unbound/test/unbound.conf:29: error: unknown keyword 'infra-keep-probing'
          /var/unbound/test/unbound.conf:29: error: stray ':'
          /var/unbound/test/unbound.conf:29: error: unknown keyword 'yes'
          read /var/unbound/test/unbound.conf failed: 3 errors in configuration file
      

      2023-01-23_19-08-48.jpg

      It is not an option to reinstall / factory reset the router.

      Can anyone help me with how to REM, "# " or delete that 29th line from booth var/unbound and /var/unbound/test unbound.conf?

      Or is there a way to "reset" the unbound configuration?

      Thank you, everyone

      R 1 Reply Last reply Reply Quote 0
      • R Offline
        rcoleman-netgate Netgate @ic_attila
        last edited by

        @ic_attila Use the GUI -- go to Diagnostics and choose "Edit File" and then load the file, make your change, and save.

        Also -- do this at your own risk as it might result in a non-functional system where the only method to resolve is to reinstall. Always make backups of the files you are editing... in your case copy/paste the file values into a text file on your computer before making those changes.

        Ryan
        Repeat, after me: MESH IS THE DEVIL! MESH IS THE DEVIL!
        Requesting firmware for your Netgate device? https://go.netgate.com
        Switching: Mikrotik, Netgear, Extreme
        Wireless: Aruba, Ubiquiti

        I 1 Reply Last reply Reply Quote 0
        • I Offline
          ic_attila @rcoleman-netgate
          last edited by

          @rcoleman-netgate Thank you for the idea. I haven't thought to edit a file in this way. Unfortunately, it didn't solve the problem. If I add a # at the begging of the 29th line (or even delete the entire line) and I press save, and reopen the file, it seems ok. But if I go to services and try to do any modification on the DNS resolver / General settings page, and press save at the bottom, the error message appears again.

          S 1 Reply Last reply Reply Quote 0
          • S Offline
            SteveITS Rebel Alliance @ic_attila
            last edited by SteveITS

            @ic_attila I have not seen that problem, however, on one of our 22.05 routers I see this in the Advanced settings for DNS Resolver, which is checked for us:

            Keep Probing

            Keep probing servers that are down

            What is on line 28? Maybe that is the actual problem line. Computers are fun that way...

            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 reboot, or more depending on packages, and device or disk speed.
            Upvote ๐Ÿ‘ helpful posts!

            I 1 Reply Last reply Reply Quote 0
            • I Offline
              ic_attila @SteveITS
              last edited by

              @steveits this is from the unbound.conf line 28-29-30

              jostle-timeout: 200
              infra-keep-probing: yes
              infra-host-ttl: 900
              

              As you mentioned, it's on the Advanced Settings tab

              2023-01-23_23-31-06.jpg

              But it is completely ignored, what I do on the GUI. It no matters if I tick, or un-tick it.

              I save it either way,

              2023-01-23_23-34-40.jpg

              apply changes, and thinks it is OK.

              2023-01-23_23-34-54.jpg

              But if I open the unbound.conf (no matter if it is the /var/unbound/test or the /var/unbound location) I see

              infra-keep-probing: yes
              
              

              I'm thinking the changes I make in the GUI are not written in the config file.

              S 1 Reply Last reply Reply Quote 0
              • bmeeksB Offline
                bmeeks
                last edited by bmeeks

                Do you have a Netgate appliance or some other device with a solid state disk system? One possibility is your disk storage has become damaged or otherwise has reverted to a read-only operating mode. Some others have posted with similar read-only issues in the past - particularly when using some type of flash memory storage. If you can't save direct file edits, that certainly sounds like a possibility.

                1 Reply Last reply Reply Quote 0
                • S Offline
                  SteveITS Rebel Alliance @ic_attila
                  last edited by

                  @ic_attila said in DNS Resolver / General settings | Unable to save changes:

                  jostle-timeout: 200
                  infra-keep-probing: yes
                  infra-host-ttl: 900

                  I have all of those lines in the router I just pulled up.

                  re: bmeeks' suggestion, see https://docs.netgate.com/pfsense/en/latest/troubleshooting/disk-lifetime.html

                  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 reboot, or more depending on packages, and device or disk speed.
                  Upvote ๐Ÿ‘ helpful posts!

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