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

DNS Resolver not resolving part 1234

Scheduled Pinned Locked Moved DHCP and DNS
41 Posts 4 Posters 5.1k 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.
  • H
    henkbart @jrey
    last edited by Dec 12, 2023, 1:04 PM

    @jrey

    When doing a PKG v i got

    unbound-1.18.0_1

    So it was updated

    1 Reply Last reply Reply Quote 1
    • H
      henkbart @johnpoz
      last edited by Dec 12, 2023, 1:06 PM

      @johnpoz

      I already got the 1.18.0_1 version

      Thank you.

      1 Reply Last reply Reply Quote 0
      • J
        jrey @johnpoz
        last edited by Dec 12, 2023, 1:16 PM

        @jrey said in DNS Resolver not resolving part 1234:

        I've never had an issue with DNS resolver stopping or "Freezing"

        and

        @johnpoz said in DNS Resolver not resolving part 1234:

        I don't recall ever having any issue where unbound just wouldn't resolve, but was still running

        yup this ^

        H 1 Reply Last reply Dec 12, 2023, 1:24 PM Reply Quote 0
        • G
          Gertjan @henkbart
          last edited by Gertjan Dec 12, 2023, 1:22 PM Dec 12, 2023, 1:20 PM

          @henkbart said in DNS Resolver not resolving part 1234:

          45451 - Is 0:00.00 /usr/local/sbin/dhcpleases -l /var/dhcpd/var/db/dhcpd.leases -d private.lan -p /var/run/unbound.pid -u /var/unbound/dhcpleases_entries.conf -h /etc/hosts

          This is the one I was talking about when I mentioned the Resolver "DHCP Client Registration" check box, the option you don't have (under Services > DNS Resolver > General Settings) as you are running Kea ..... as in that case the option doesn't show up.
          Is this correct, are you using Kea ?
          Or Dhcpd ?

          If you are using kea, you should see this :

          2564b4db-544c-421b-954b-76a1cf5baca3-image.png

          If you are using kea, this process "/usr/local/sbin/dhcpleases" can not - should not exist.
          As this is the one that shoots unbound in the face every time ..... see above.

          edit :

          You have this :

          e9db5c3e-a9ef-4c9a-b3b0-e151e59b9770-image.png

          == kea DHCP checked ?

          No "help me" PM's please. Use the forum, the community will thank you.
          Edit : and where are the logs ??

          H 1 Reply Last reply Dec 12, 2023, 1:27 PM Reply Quote 0
          • H
            henkbart @jrey
            last edited by Dec 12, 2023, 1:24 PM

            @jrey

            Lucky you,

            But there are a lot of people having troubles with it, including me.
            That makes it difficult to pinpoint the location of the problem....

            J 1 Reply Last reply Dec 12, 2023, 1:38 PM Reply Quote 0
            • H
              henkbart @Gertjan
              last edited by Dec 12, 2023, 1:27 PM

              @Gertjan
              Yes i have the Kea DHCP enabled.

              G 1 Reply Last reply Dec 12, 2023, 1:28 PM Reply Quote 0
              • G
                Gertjan @henkbart
                last edited by Gertjan Dec 12, 2023, 1:29 PM Dec 12, 2023, 1:28 PM

                @henkbart

                Can you re confirm that this one :

                5435d4d7-4aeb-499a-a80b-1ef81e0476ae-image.png

                = dhcpleases process - maybe it has another pid now - is still running ?

                No "help me" PM's please. Use the forum, the community will thank you.
                Edit : and where are the logs ??

                H 1 Reply Last reply Dec 12, 2023, 1:34 PM Reply Quote 0
                • H
                  henkbart @Gertjan
                  last edited by Dec 12, 2023, 1:34 PM

                  @Gertjan

                  Yes,
                  45451 root 1 52 0 12M 2252K kqread 1 0:00 0.00% dhcpleases

                  is still running

                  G 1 Reply Last reply Dec 12, 2023, 3:32 PM Reply Quote 0
                  • J
                    jrey @henkbart
                    last edited by jrey Dec 12, 2023, 1:40 PM Dec 12, 2023, 1:38 PM

                    @henkbart said in DNS Resolver not resolving part 1234:

                    Lucky you,

                    But I think the point being made by both myself and @johnpoz is that is not likely a unbound issue as such.

                    many people do indeed report problems and when doing so they are assuming it to be unbound because that is what they see. But that is generally not the root cause..
                    They see the effect, not the cause.

                    unbound generally just works. Right out of the box.

                    That's all we are saying.

                    @Gertjan is giving you some good advice on things to look for. including the current path you are on: re: DHCP.
                    edit: however if DHCP is causing the issue, you'd likely see a stream of unbound restarts and you say they are not there in the log.

                    H 1 Reply Last reply Dec 12, 2023, 1:48 PM Reply Quote 1
                    • H
                      henkbart @jrey
                      last edited by henkbart Dec 12, 2023, 1:50 PM Dec 12, 2023, 1:48 PM

                      @jrey

                      The problem is, that every now and then (and that could be weeks) i loses the ability to connect to the internet.
                      I have my own PBX here that uses VOIP and SIP trunks.
                      Some time they can no register with the host.
                      And from that time, also no other can connect to any internet address.
                      Modem is UP,
                      WAN is UP.
                      LAN is UP.
                      Than all DHCP mus fail because the are on differnt ip addresses.
                      But also no entries in the log files to give any clue.

                      So where to look else for....

                      J G 2 Replies Last reply Dec 12, 2023, 2:16 PM Reply Quote 0
                      • J
                        jrey @henkbart
                        last edited by Dec 12, 2023, 2:16 PM

                        @henkbart said in DNS Resolver not resolving part 1234:

                        The problem is, that every now and then (and that could be weeks) i loses the ability to connect to the internet.

                        sounds interesting. so when you "lose the ability to connect to the internet" unbound would not be able to up stream resolve, but would still be running. If it can't talk upstream how would it resolve.

                        so the question you might start looking into is why have you lost ability to connect to the internet?

                        do you have a timestamp from the last time this happened?

                        check the logs (not unbound logs specifically) for events that might tell you why you lost the internet.

                        If you can't find anything in current logs regarding the last time it happened

                        Then the next time it does.... do this...

                        @johnpoz said in DNS Resolver not resolving part 1234:

                        A good test might be to try and resolve something just local.. say your pfsense fqdn via your fav local tool, nslookup, dig, host, doggo, etc.. Does that work, just not external? Its best to use a cmd line tool because then you can see the actual response from unbound, be it NX or servfail, refused, etc.

                        1 Reply Last reply Reply Quote 0
                        • G
                          Gertjan @henkbart
                          last edited by Dec 12, 2023, 3:32 PM

                          @henkbart said in DNS Resolver not resolving part 1234:

                          45451 root 1 52 0 12M 2252K kqread 1 0:00 0.00% dhcpleases

                          Ok.
                          Doesn't make any sense.

                          I propose :
                          Switch back to 'dhcp' mode.
                          Save.
                          Goto the Resolver settings.
                          Now, the DHCP Client registration (and "Static DHCP Client Registration") should be visible.
                          Note that your "DHCP Client registration" is checked - is this the case ?
                          Uncheck it.
                          Save, and then Apply.

                          Go back to System > Advanced > Networking and select kea again.

                          The "dhcpleases" process is gone now. Correct ?

                          Btw :
                          As far as I can see on my my pfSense, while using kea, the /var/dhcpd/var/db/dhcpd.leases file isn't used. That file is "watched" by the dhcpleases process, and if it changes, unbound is send a signal to restart.
                          So, harmess, I guess.
                          But still, strange, as it should even be started in the first place.

                          No "help me" PM's please. Use the forum, the community will thank you.
                          Edit : and where are the logs ??

                          H 1 Reply Last reply Dec 12, 2023, 3:56 PM Reply Quote 0
                          • G
                            Gertjan @henkbart
                            last edited by Dec 12, 2023, 3:46 PM

                            @henkbart said in DNS Resolver not resolving part 1234:

                            The problem is, that every now and then (and that could be weeks) i loses the ability to connect to the internet.

                            You can check your uplink quality.

                            15c274b4-846b-4b94-bac5-57ad1067ebcc-image.png

                            It should be constant, flat and as small as possible.
                            If it start to go up and down, or worse :

                            1. you are saturating your connection, and if the 'pipe', up or down is to full, dpinger starts to miss ping packets, it can go in panic mode, and 'restart' your WAN interface.
                              No need to explain that if the pipe (uplink) is bad or full, or not working well, the resolver can't do its work neither. Right ?
                              .....
                            2. call your ISP and say : good bye, I'll leave you for a better one.

                            No "help me" PM's please. Use the forum, the community will thank you.
                            Edit : and where are the logs ??

                            J H 3 Replies Last reply Dec 12, 2023, 3:56 PM Reply Quote 0
                            • H
                              henkbart @Gertjan
                              last edited by Dec 12, 2023, 3:56 PM

                              @Gertjan
                              Hello,
                              I did what you wrote.
                              Enable DHCP.
                              Got :
                              FireShot Pro Webpage Capture 278 - 'firewall.private.lan - Services_ DNS Resolver_ General Settings' - 192.168.1.1.png

                              So disabled the DHCP Client Registration.
                              Saved it.
                              And then switch to KEA

                              And the dhcpleases is gone now.

                              1 Reply Last reply Reply Quote 0
                              • J
                                jrey @Gertjan
                                last edited by jrey Dec 12, 2023, 3:57 PM Dec 12, 2023, 3:56 PM

                                @Gertjan said in DNS Resolver not resolving part 1234:

                                dpinger starts to miss ping packets,

                                if that's the problem OP might be able to mitigate some of that by changing the ping times / loss interval etc or by selecting a different monitor IP. (if that is even setup)

                                Most users wouldn't notice the difference between the default 500ms setting and even 2-3-4 or 5 seconds.

                                if Applicable OP could look https://docs.netgate.com/pfsense/en/latest/routing/gateway-configure.html

                                for the Probe Interval, Loss Interval, Time Period, and Alert Interval seeing how the adjusts could be made and the rules to follow.

                                1 Reply Last reply Reply Quote 0
                                • H
                                  henkbart @Gertjan
                                  last edited by Dec 12, 2023, 4:03 PM

                                  @Gertjan
                                  Here is mine

                                  FireShot Pro Webpage Capture 279 - 'firewall.private.lan - Status_ Monitoring' - 192.168.1.1.png

                                  1 Reply Last reply Reply Quote 0
                                  • J
                                    jrey @Gertjan
                                    last edited by Dec 12, 2023, 4:20 PM

                                    @Gertjan said in DNS Resolver not resolving part 1234:

                                    It should be constant, flat and as small as possible.

                                    Like anything, that depends a lot on scaling resolution, duration of sample as well as the connection. Great guideline but not to be interpreted as a blanket statement.

                                    For example, the scaling that appears on the graphs, when everything is mostly sub 1ms as shown from my system the graph appears much less flat, but doesn't mean there is a problem.

                                    Screen Shot 2023-12-12 at 11.06.59 AM.png

                                    Looking at the data summary under the pretty graph might tell us more ?

                                    Screen Shot 2023-12-12 at 11.18.51 AM.png

                                    H 1 Reply Last reply Dec 12, 2023, 5:48 PM Reply Quote 0
                                    • H
                                      henkbart @jrey
                                      last edited by Dec 12, 2023, 5:48 PM

                                      @jrey

                                      FireShot Pro Webpage Capture 280 - 'firewall.private.lan - Status_ Monitoring' - 192.168.1.1.png

                                      That is mine

                                      J 2 Replies Last reply Dec 12, 2023, 6:13 PM Reply Quote 0
                                      • J
                                        jrey @henkbart
                                        last edited by Dec 12, 2023, 6:13 PM

                                        @henkbart

                                        Nothing really interesting here, did you have an issue with connectivity as you've described in the past day?

                                        1 Reply Last reply Reply Quote 0
                                        • J
                                          jrey @henkbart
                                          last edited by Dec 12, 2023, 6:39 PM

                                          @henkbart

                                          Anything interesting in

                                          System Logs > System (Tab) -> Gateways (Tab)?

                                          H 1 Reply Last reply Dec 12, 2023, 8:16 PM Reply Quote 0
                                          39 out of 41
                                          • First post
                                            39/41
                                            Last post
                                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                                            This community forum collects and processes your personal information.
                                            consent.not_received