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
    61 Posts 12 Posters 14.7k Views 11 Watching
    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.
    • ? Offline
      A Former User @stephenw10
      last edited by

      @stephenw10

      ...and freedns... and hetzner... and hurricane electrics is failing too with ipv6.....

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

        Ah, that's good info. Ok...

        1 Reply Last reply Reply Quote 0
        • M Offline
          m80s @stephenw10
          last edited by

          @stephenw10 in my case I tried with 25.07.1:

          • DuckDNS
          • DeSec

          both with IPv4 and both failing.
          No issue on 24.11.

          Now i reverted back to 24.11 so I can't make further tests

          M stephenw10S 2 Replies Last reply Reply Quote 0
          • M Online
            mcury Rebel Alliance @m80s
            last edited by

            @m80s said in Update 2.7.2 to 2.8.0 Dynamic DNS not working with Cloudflare:

            DuckDNS

            I'm running 25.07.1 and duckdns is working for me.

            dead on arrival, nowhere to be found.

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

              @m80s said in Update 2.7.2 to 2.8.0 Dynamic DNS not working with Cloudflare:

              @stephenw10 in my case I tried with 25.07.1:

              DuckDNS
              DeSec
              

              both with IPv4 and both failing.

              Yeah that's unexpected. Unless they are using a WAN with a gateway that shows as down. In which case you would be hitting the new behaviour requiring gateway monitoring be corrected.

              M 1 Reply Last reply Reply Quote 0
              • M Offline
                m80s @stephenw10
                last edited by

                @stephenw10

                tried again with 25.07.01 and confirmed I need to set Disable Gateway Monitoring Action to make it work.

                I think this behavior should be fixed

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

                  Well that's not a bug if the gateways used were marked as down. That's the expected behaviour in 2.8.X.

                  If the gateway being marked down is a change since 2.7.2 that could be a separate problem.

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

                    @stephenw10 Hello i am not sure to understand the workaround or the solution.

                    I just update from 2.7.X to 2.8.1 and Dyndns doesn't show IP on dashboard (N/A and time)

                    • IP string is correctly showed on diag php command
                    • checkip.dyndns.org is OK
                    • i create an additonnal checkipservice on my website to be sure

                    What we must do step by step to fix this problem please.

                    Thanks
                    regards

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

                      Are you running it on an interface that has a gateway shown as down? If so change the target to something that responds or set it to unmonitored.

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

                        @stephenw10 Hello, It appears that the gateway was indeed listed as offline because originally it was using the internet provider's gateway IP address, and the provider had blocked ICMP ping requests. Therefore, you simply need to enter a reliable IP address that accepts ICMP pings, such as 8.8.8.8, 8.8.4.4, 1.1.1.1, etc.

                        Check gateway:
                        Stats -> Gateways
                        Check if Gateways is marked offline (red)

                        Put a realiable IP to check 'online availability':
                        System -> Routing -> Gateways
                        Click on little pencil to gateways and change Monitored IP field with 8.8.8.8 or 8.8.4.4 or any other Ip that you known which can be pinged 24/24 - 7/7
                        Your gateways will be properly checked to determine if they are online or not.

                        This way you don't disable anything, you actually improve your configuration :)

                        I hope this can help others. Thank you @stephenw10

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