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

    strange unbound issue

    DHCP and DNS
    3
    9
    403
    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.
    • J
      JohnDow
      last edited by JohnDow

      not resolve web.whatsapp.com

      but all other work and resolve.
      mystics, please help with diagnostics.

      dns_whatsap.png

      ||dns_google.png

      GertjanG J 2 Replies Last reply Reply Quote 0
      • GertjanG
        Gertjan @JohnDow
        last edited by Gertjan

        @JohnDow said in strange unbound issue:

        web.whatsapp.com

        Not hard :

        77c237ad-dc8a-49eb-b5d7-55df8e173880-image.png

        so no one "picks up the phone" at 127.0.0.1 port 53. This means : unbound isn't running (or brain dead).

        Let start with the basics :
        What is your pfSense version ?
        Running bare bone, VM, other ?
        What were the other DNS settings you've changed ?
        Go to Services >DNS Resolver > General Settings and at the bottom (nearly) of the page hit Save - and then Apply at the top of the page. Now go to the page with the answers : Status > System Logs > System > DNS Resolver : what happened ?

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

        J 1 Reply Last reply Reply Quote 0
        • J
          JohnDow @JohnDow
          last edited by

          This post is deleted!
          1 Reply Last reply Reply Quote 0
          • J
            JohnDow @Gertjan
            last edited by JohnDow

            @Gertjan said in strange unbound issue:

            his means : unbound isn't running (or brain dead).
            it work in all other sites

            but **all other work and resolve**.
            

            in second pics resolve google

            Version 2.7.1-RELEASE (amd64)
            built on Wed Nov 29 23:08:00
            FreeBSD 14.0-CURRENT
            work on non brand old (2lans) comp
            until update 2.7.1 unbound work perfectly.
            0 ms but not resolve only web.whatsapp.com

            dns_whatsap3.png

            GertjanG 1 Reply Last reply Reply Quote 0
            • GertjanG
              Gertjan @JohnDow
              last edited by Gertjan

              @JohnDow said in strange unbound issue:

              0 ms but not resolve only web.whatsapp.com

              dd8c3190-3986-4bbd-a6b2-ff3e57fb03cc-image.png

              For whatever reason, your "Results" part is missing.

              unbound, this time, replied within "0 ms", the others within 17 ms.
              But no answer - for you. I did have an answer.
              That for you, 8.8.8.8 hasn't an answer neither .... that's puzzling.

              If I ask "8.8.8.8" manually :

              [23.09-RELEASE][root@pfSense.bhf.tld]/root: dig @8.8.8.8 web.whatsapp.com +short
              mmx-ds.cdn.whatsapp.net.
              31.13.83.51
              

              Try this one for yourself.

              Can you also show a :

              dig web.whatsapp.com
              

              ?

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

              J 2 Replies Last reply Reply Quote 0
              • J
                JohnDow @Gertjan
                last edited by

                This post is deleted!
                1 Reply Last reply Reply Quote 0
                • J
                  JohnDow @Gertjan
                  last edited by

                  @Gertjan said in strange unbound issue:

                  dig web.whatsapp.com

                  Shell Output - dig web.whatsapp.com

                  ;; communications error to 127.0.0.1#53: timed out
                  ;; communications error to 127.0.0.1#53: timed out
                  ;; communications error to 127.0.0.1#53: timed out

                  ; <<>> DiG 9.18.19 <<>> web.whatsapp.com
                  ;; global options: +cmd
                  ;; Got answer:
                  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1471
                  ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

                  ;; OPT PSEUDOSECTION:
                  ; EDNS: version: 0, flags:; udp: 4096
                  ;; QUESTION SECTION:
                  ;web.whatsapp.com. IN A

                  ;; ANSWER SECTION:
                  web.whatsapp.com. 37 IN CNAME mmx-ds.cdn.whatsapp.net.
                  mmx-ds.cdn.whatsapp.net. 38 IN A 157.240.0.60

                  ;; Query time: 18 msec
                  ;; SERVER: 77.88.8.8#53(77.88.8.8) (UDP)
                  ;; WHEN: Wed Dec 06 16:57:20 MSK 2023
                  ;; MSG SIZE rcvd: 98

                  Shell Output - dig @8.8.8.8 web.whatsapp.com +short

                  mmx-ds.cdn.whatsapp.net.
                  157.240.205.60

                  S GertjanG 2 Replies Last reply Reply Quote 0
                  • S
                    SteveITS Galactic Empire @JohnDow
                    last edited by

                    @JohnDow said in strange unbound issue:

                    ;; communications error to 127.0.0.1#53: timed out

                    So as noted is unbound (DNS Resolver) running? Check Status/DNS Resolver and the icons at the top bar.

                    In System/General Setup to what is "DNS Resolution Behavior" set?

                    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
                    • GertjanG
                      Gertjan @JohnDow
                      last edited by

                      @JohnDow

                      Can you open up a console, or better, a SSH session, use option 8 ( Shell ) and use this command :

                      tail -f /var/log/resolver.log
                      

                      and tell, show us, what you saw ?

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

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