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

    DNS Resolver Error

    Scheduled Pinned Locked Moved
    Official Netgate® Hardware
    4
    5
    1.2k
    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.
    • K
      kkris
      last edited by

      Hello forum

      Netgate 7100U
      22.05-RELEASE (amd64)

      We just purchased a new firewall and the DNS Resolver shows errors. Also, clients can't reach domain names when the pfSense is set as DNS-server. We configured external DNS-servers on the clients for now and the problem (for them) is gone. I believe the error messages below and the DNS issues on the clients are somehow connected.

      Oct 1 03:43:50 unbound 77679 [77679:1] error: recvfrom 24 failed: Protocol not available
      Oct 1 03:43:50 unbound 77679 [77679:1] error: recvfrom 23 failed: Protocol not available
      Oct 1 03:43:51 unbound 77679 [77679:1] error: recvfrom 24 failed: Protocol not available
      Oct 1 03:43:52 unbound 77679 [77679:1] error: recvfrom 23 failed: Protocol not available
      Oct 1 03:43:53 unbound 77679 [77679:1] error: recvfrom 24 failed: Protocol not available
      Oct 1 03:43:55 unbound 77679 [77679:1] error: recvfrom 23 failed: Protocol not available
      Oct 1 03:43:58 unbound 77679 [77679:1] error: recvfrom 24 failed: Protocol not available
      Oct 1 03:44:01 unbound 77679 [77679:1] error: recvfrom 23 failed: Protocol not available
      Oct 1 03:44:05 unbound 77679 [77679:2] error: recvfrom 24 failed: Protocol not available
      Oct 1 04:04:55 unbound 77679 [77679:2] error: recvfrom 24 failed: Protocol not available
      Oct 1 04:04:55 unbound 77679 [77679:0] error: recvfrom 23 failed: Protocol not available
      Oct 1 04:04:55 unbound 77679 [77679:2] error: recvfrom 25 failed: Protocol not available
      Oct 1 04:04:55 unbound 77679 [77679:0] error: recvfrom 24 failed: Protocol not available
      Oct 1 04:04:55 unbound 77679 [77679:2] error: recvfrom 23 failed: Protocol not available
      Oct 1 04:04:56 unbound 77679 [77679:0] error: recvfrom 24 failed: Protocol not available
      Oct 1 04:04:56 unbound 77679 [77679:2] error: recvfrom 25 failed: Protocol not available
      Oct 1 04:04:57 unbound 77679 [77679:2] error: recvfrom 25 failed: Protocol not available

      We have several pfSense firewalls running and none of them shows this behavior. Could you please point me in the right direction here? :) Thank you very much!

      Cheers,
      Kris

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

        @kkris It works out of the box…. Post your DNS Resolver settings?
        Any firewall rules that might affect DNS/port 53/TCP or UDP?
        If it’s new and you haven’t changed much you could always make a backup and try Diagnostics/Factory Defaults.

        Pre-2.7.2/23.09: 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 restart, or more depending on packages and device speed.
        Upvote 👍 helpful posts!

        1 Reply Last reply Reply Quote 0
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

          Does that site have IPv6 where the others do not?

          1 Reply Last reply Reply Quote 0
          • K
            kkris
            last edited by

            Hello

            Sorry for the very late reply and thanks so much for your input.

            @stephenw10 I deactivated IPv6 on the WAN interface and the errors are gone now. Thanks again!

            Kind regards and have a nice weekend :)
            Kris

            M 1 Reply Last reply Reply Quote 0
            • M
              MarkStrut @kkris
              last edited by

              @kkris That was so simple - I have spend all day trying to figure it out - then did what you suggested and bang ... fixed. Cheers

              1 Reply Last reply Reply Quote 0
              • First post
                Last post