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 4.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.
    • fireodoF
      fireodo @power_matz
      last edited by

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

      I added both services. Without any success

      OHhh - so there must be, in your case, a other cause for not getting the pppoe0 adress ... 🤔
      I have here also dyndns with pppoe but not with cloudflare as provider ...🤔

      Kettop Mi4300YL CPU: i5-4300Y @ 1.60GHz RAM: 8GB Ethernet Ports: 4
      SSD: SanDisk pSSD-S2 16GB (ZFS) WiFi: WLE200NX
      pfsense 2.8.0 CE
      Packages: Apcupsd, Cron, Iftop, Iperf, LCDproc, Nmap, pfBlockerNG, RRD_Summary, Shellcmd, Snort, Speedtest, System_Patches.

      1 Reply Last reply Reply Quote 0
      • fireodoF
        fireodo @stephenw10
        last edited by

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

        Is everyone hitting this using pppoe by chance?

        I have pppoe here too but not cloudflare dyndns - i guess its something specific to cloudflare ... 🤔

        Kettop Mi4300YL CPU: i5-4300Y @ 1.60GHz RAM: 8GB Ethernet Ports: 4
        SSD: SanDisk pSSD-S2 16GB (ZFS) WiFi: WLE200NX
        pfsense 2.8.0 CE
        Packages: Apcupsd, Cron, Iftop, Iperf, LCDproc, Nmap, pfBlockerNG, RRD_Summary, Shellcmd, Snort, Speedtest, System_Patches.

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

          @stephenw10 same output here. it show my correct ip8303b1e7-bae0-4d44-a1e4-715311b3f78a-image.png
          i've tried the webpage also return the correct ip
          43cd85b9-6cf4-4e73-9def-531038010f4b-image.png
          @fireodo i've added both of sites, same result
          b8262768-6ba7-4612-8138-af1738c7c214-image.png

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

            Hmm, the error it's showing should be independent of the service in use. It tries to read the IP, checks its a valid IP address and fails that check.

            I'm wondering if it's passing the wrong interface type after the pppoe changes hence asking if anyone is hitting it on a non-pppoe wan?

            Also is anyone using using not the actual 'wan'? Like opt1, opt2 etc?

            P 1 Reply Last reply Reply Quote 0
            • P
              power_matz @stephenw10
              last edited by

              @stephenw10 Just to clarify: I am still using the old module, not the new if_pppoe kernel module for PPPoE client

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

                Ok. It may still be the issue though as the pppoe code was changed to allow both connection types.

                P 1 Reply Last reply Reply Quote 0
                • P
                  power_matz @stephenw10
                  last edited by

                  @stephenw10 Just configured another DynDNS Service and switched to the new if_pppoe kernel module. The problem is still there

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

                    Only after switching to if_pppoe?

                    Which interface are you using pppoe on? The actual 'wan' interface?

                    P 1 Reply Last reply Reply Quote 0
                    • P
                      power_matz @stephenw10
                      last edited by

                      @stephenw10 before and after switching. Just wanted to confirm that the new if_pppoe module is not the culprit.
                      I am using the 'wan' interface

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

                        Hello.
                        I am experiencing the same faulty behavior.
                        When debugging the PHP-Command in pfSense, it returns an IPv6 in my case.

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

                          When querying pppoe0?

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

                            @stephenw10
                            Yes.
                            Still quite common in Germany. (V)DSL so it's based on pppoe.

                            Dynamic DNS updates stopped working just as 2.8.0 was installed. Quite a bummer for me because I am heavily depended on that function.
                            I also tested it with the old pppoe driver and the new one - same behavior, despite I am not using cloudflare.

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

                              Do you only have an IPv6 address there?

                              I'm using PPPoE over VDSL here and it work fine. There must be something else in play.

                              D 1 Reply Last reply Reply Quote 0
                              • 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
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.