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

    Update 2.7.2 to 2.8.0 Dynamic DNS not working with Cloudflare

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    39 Posts 7 Posters 3.5k 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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      Is your upstream gateway shown as online?

      In 2.8.0 (and 25.03) dyndns update will fail if the gateway is offline.

      D 1 Reply Last reply Reply Quote 0
      • D
        djstone @stephenw10
        last edited by

        @stephenw10
        Nope, it's dual stack (IPv4 and IPv6)

        1 Reply Last reply Reply Quote 0
        • D
          djstone @stephenw10
          last edited by

          @stephenw10
          It's indeed offline.
          I just changed it to unmonitored and, who would have thought, the DynDNS update is working again.

          D 1 Reply Last reply Reply Quote 1
          • D
            djstone @djstone
            last edited by

            @djstone
            ok, I'll have to correct that statement - IPv6 worked. IPv4 shows "0.0.0.0" as IP.

            D 1 Reply Last reply Reply Quote 0
            • D
              djstone @djstone
              last edited by

              @djstone
              I think the cause for the IPv4 address not updating might be, that I already did it via another service. Will restart the pppoe connection and see if it comes back to live correctly.

              1 Reply Last reply Reply Quote 1
              • D
                djstone
                last edited by

                Ok, so far the gateway status seems to have been the root cause. Thank you for your fast response.
                It would be nice, if one checks "verbose" on the Dynamic DNS configuration, to actually receive a verbose ouput or at least a hint to why the update failed.

                Last thing I see me having to do is dig into the php source code to find the possible causes.
                Thanks again.

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

                  Yup I agree. Let me see about adding some debugging there.

                  1 Reply Last reply Reply Quote 0
                  • N
                    nation
                    last edited by

                    Thank you @stephenw10. That worked for me also.

                    1 Reply Last reply Reply Quote 1
                    • T
                      TheBigS
                      last edited by

                      Is there any news about the problem, or is there a workaround?

                      1 Reply Last reply Reply Quote 0
                      • M
                        Mocha9973
                        last edited by

                        Trying to follow along, not tried everything you guys did but found this post and that worked for me.

                        Turned of Gateway monitoring only and Dynamic DNS became online at once after a force refresh.

                        https://www.reddit.com/r/PFSENSE/comments/1kngpej/ddns_using_cloudflare_stopped_working_after/

                        1 Reply Last reply Reply Quote 0
                        • N
                          nation
                          last edited by

                          @TheBigS try to check the option. For me worked
                          26e6f3f0-6ddb-41e1-ab49-9d7bbdf22cab-image.png

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

                            Yup the change of behaviour here is that the client checks the WAN is up by the gateway status on it before it tries to update. So if your gateway monitoring shows as offline the best solution here is to correct that so it's pinging something that responds. An alternative is to just mark the gateway as always up so it doesn't get monitored but then you lose gateway data.

                            T 1 Reply Last reply Reply Quote 0
                            • T
                              TheBigS @stephenw10
                              last edited by

                              @stephenw10 thanks a lot. my pfsense is now pinging quad9 and now everything is working. 👍🏻

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