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

    Unbound resolver error: Can't assign requested address for 127.0.0.1

    DHCP and DNS
    dns dns resolver unbound configuration config
    5
    40
    6.5k
    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.
    • RonpfSR
      RonpfS
      last edited by RonpfS

      Those tables : pfB_PRI1_v4, pfB_PRI4_v4, pfB_PRI2_v4, DNSBL_pfB_PRI2_v4 - pfB_PRI2_v4, DNSBL_Abuse - pfB_Abuse_PS_v4 shouldn't be in DNSBL, they are IPv4 tables, remove them.

      Disable BBC_DGA it's probably too big for your memory. And try another Force Reload DNSBL.

      You have to monitor memory usage with Status Monitoring. The Dashboard only display "current" memory usage, the Monitoring will give you memory usage over time.

      T 1 Reply Last reply Reply Quote 0
      • T
        themadsalvi @RonpfS
        last edited by

        @RonpfS

        Removed those, and forced a reload, which still had the unbound resolver error.

        This is the result in the status monitoring during and after reload
        a348ed5f-d979-4a1d-8682-09de6ce8d317-image.png

        This is the force reload log
        pfblockerng2.txt

        1 Reply Last reply Reply Quote 0
        • RonpfSR
          RonpfS
          last edited by RonpfS

          You still have pfB_Abuse_PS_v4 to remove
          Try again with BBC_DGA feed disabled.
          If it still fails, then post your DNS Resolver config.

          1 Reply Last reply Reply Quote 0
          • T
            themadsalvi
            last edited by themadsalvi

            @RonpfS @Gertjan
            Here is the latest file for the reload, with all of the lists gone that you told me to delete. Same error pops up:
            pfblockerng3.txt

            cf0bfbbe-1751-4061-ad22-a07e5446cad1-image.png

            Rsolver settings.

            7a119d6b-0902-4162-b897-22902e3ce6d5-image.png

            211b1b7c-c022-4d22-874c-7cd89b024aa8-image.png

            b1b1b841-63b2-420c-ac63-134932daf8e6-image.png

            2a21e6fb-65bd-4ff2-a3cc-08c1069244f7-image.png

            eadfb9b5-9ce4-4979-a97c-683a4da03377-image.png

            1 Reply Last reply Reply Quote 0
            • RonpfSR
              RonpfS
              last edited by

              Did you try to remove the private-domain: line ?
              On my box I have Prefetch Support and Prefetch DNS Key Support ticked.

              T 1 Reply Last reply Reply Quote 0
              • T
                themadsalvi @RonpfS
                last edited by

                @RonpfS @Gertjan
                I ended up taking the private domain line out(save and apply), then checking the prefetch support and Prefetch DNS Key Support boxes(save and apply changes). Tried the forced reload, with those changes, and the error persists.

                1 Reply Last reply Reply Quote 0
                • RonpfSR
                  RonpfS
                  last edited by

                  In a shell or Diagnostics Command prompt, do a

                  ls -al /var/unbound /var/db/pfblockerng
                  
                  T 1 Reply Last reply Reply Quote 0
                  • T
                    themadsalvi @RonpfS
                    last edited by themadsalvi

                    @RonpfS @Gertjan
                    I have placed the output below

                    34befb63-1f5e-4954-9ce1-484201b12029-image.png
                    afa1750a-be0a-4525-83fb-10a5ea7153e1-image.png

                    Why are the last 4 so old?

                    RonpfSR 1 Reply Last reply Reply Quote 0
                    • RonpfSR
                      RonpfS @themadsalvi
                      last edited by RonpfS

                      @themadsalvi The 2012 timestamp looks suspicious compared to mine :

                      -rw-r-----   1 unbound  unbound       2459 Dec  8 19:42 unbound_control.key
                      -rw-r-----   1 unbound  unbound       1330 Dec  8 19:42 unbound_control.pem
                      -rw-r-----   1 unbound  unbound       2459 Dec  8 19:42 unbound_server.key
                      -rw-r-----   1 unbound  unbound       1318 Dec  8 19:42 unbound_server.pem
                      
                      

                      maybe it time to delete them, restart unbound or reboot pfsense.

                      T 1 Reply Last reply Reply Quote 0
                      • T
                        themadsalvi @RonpfS
                        last edited by themadsalvi

                        @RonpfS

                        what is the syntax for deleting the files in the shell?
                        rm -f /var/unbound/unbound_server.key?

                        is that the correct syntax?

                        Edit:
                        It looks like it was able to recreate the files
                        da3920eb-4780-4450-ab68-f3024e7e5c1d-image.png

                        RonpfSR 1 Reply Last reply Reply Quote 0
                        • RonpfSR
                          RonpfS @themadsalvi
                          last edited by RonpfS

                          @themadsalvi

                          Rename them in case :

                          mv  /var/unbound/unbound_control.key /var/unbound/backup_unbound_control.key
                          mv  /var/unbound/unbound_control.pem /var/unbound/backup_unbound_control.pem
                          mv  /var/unbound/unbound_server.key /var/unbound/backup_unbound_server.key
                          mv  /var/unbound/unbound_server.pem /var/unbound/backup_unbound_server.pem
                          

                          restart unbound, it should start, if not ... then move them back.
                          to remove them it's :

                          rm /var/unbound/unbound_server.pem
                          

                          Also it's better to access the webgui with the pfsense IP address instead of using it's domain name when stopping and restarting DNS resolver.

                          T 1 Reply Last reply Reply Quote 0
                          • T
                            themadsalvi @RonpfS
                            last edited by themadsalvi

                            @RonpfS
                            unbound restarted ok, without any errors, but the DNSBL was still unable to reload without the error.
                            pfblockerng4.txt

                            I use the IP of Pfsense whenever I log into the web GUI, not sure why it uses the domain name when logging into shell

                            1 Reply Last reply Reply Quote 0
                            • GrimsonG
                              Grimson Banned
                              last edited by

                              What other packages are you using? Bind will conflict with unbound and if you use Service Watchdog make sure it does not monitor unbound.

                              1 Reply Last reply Reply Quote 0
                              • RonpfSR
                                RonpfS
                                last edited by

                                This post is deleted!
                                1 Reply Last reply Reply Quote 0
                                • RonpfSR
                                  RonpfS
                                  last edited by RonpfS

                                  Well ... I have no more clue why it doesn't reload unbound.
                                  Maybe disable all feeds excepts Ads ?

                                  What does ls -al /var/unbound look like now ?

                                  T 1 Reply Last reply Reply Quote 0
                                  • T
                                    themadsalvi @RonpfS
                                    last edited by themadsalvi

                                    @RonpfS I placed the result of the rebuilt key and pem files, as well as how /var/unbound looks in my last post(out on lunch and on mobile, sorry)

                                    @Grimson the one thing I find odd is it just started this over the weekend, after a power outage. It has been fine for the last 6 months, without any issue. I do not have bind,and have made sure that unbound is not being monitored by service watchdog. I have the regularly installed packages like pfblockerng-devel, snort, etc.

                                    Screenshot_20190326-123300__01.jpg
                                    Screenshot_20190326-123308__01.jpg

                                    GrimsonG 1 Reply Last reply Reply Quote 0
                                    • GrimsonG
                                      Grimson Banned @themadsalvi
                                      last edited by

                                      @themadsalvi said in Unbound resolver error: Can't assign requested address for 127.0.0.1:

                                      @Grimson the one thing I find odd is it just started this over the weekend, after a power outage.

                                      So did you run fsck on the filesystem? https://docs.netgate.com/pfsense/en/latest/hardware/troubleshooting-disk-check-errors-fsck.html#manually-run-fsck

                                      I have the regularly installed packages like pfblockerng-devel, snort, etc.

                                      There are no regularly installed packages, a regular install comes without additional packages. So always mention the packages you are using when asking for help.

                                      If following the above to check the filesystem doesn't work grab a config backup and do a fresh install to make sure the installation is in a good state.

                                      T 1 Reply Last reply Reply Quote 0
                                      • T
                                        themadsalvi @Grimson
                                        last edited by

                                        @Grimson iplaced some screenshots from my mobile in my previouspost. Fsck says that /dev/zroot/ROOT cannot be opened since there is no file or directory present

                                        GrimsonG 1 Reply Last reply Reply Quote 0
                                        • GrimsonG
                                          Grimson Banned @themadsalvi
                                          last edited by

                                          @themadsalvi said in Unbound resolver error: Can't assign requested address for 127.0.0.1:

                                          @Grimson iplaced some screenshots from my mobile in my previouspost. Fsck says that /dev/zroot/ROOT cannot be opened since there is no file or directory present

                                          https://www.freebsd.org/doc/handbook/zfs-zpool.html#zfs-zpool-status
                                          https://www.freebsd.org/doc/handbook/zfs-zpool.html#zfs-zpool-scrub

                                          T 1 Reply Last reply Reply Quote 0
                                          • T
                                            themadsalvi @Grimson
                                            last edited by

                                            @Grimson
                                            0dc2224a-ee6b-455c-abea-fef25d114303-image.png

                                            It looks like it found no errors in the pool. I even ran the scrub with no errors found.

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