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

    DynDNS is broken after 2.8 update

    Scheduled Pinned Locked Moved DHCP and DNS
    12 Posts 6 Posters 1.4k 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.
    • S
      sunni
      last edited by

      Same here.
      In the logs system -> general I see this message:

      
May 31 16:48:15	php-fpm	92149	/services_dyndns_edit.php: Dynamic DNS (myfancyownhostgoeshere) There was an error trying to determine the public IP for interface - wan (pppoe0 ).
      V 1 Reply Last reply Reply Quote 0
      • F
        fyshed
        last edited by

        Same for me and same error. Waiting for someone smarter than me to figure out a fix.

        1 Reply Last reply Reply Quote 0
        • V
          Vertex @sunni
          last edited by

          @sunni said in DynDNS is broken after 2.8 update:

          Same here.
          In the logs system -> general I see this message:

          
May 31 16:48:15	php-fpm	92149	/services_dyndns_edit.php: Dynamic DNS (myfancyownhostgoeshere) There was an error trying to determine the public IP for interface - wan (pppoe0 ).

          it is exactly the same error message that i get:

          Jun 1 11:26:20	php-fpm	433	/services_dyndns_edit.php: Dynamic DNS () There was an error trying to determine the public IP for interface - wan (pppoe0 ).
Jun 1 11:30:00	php-cgi	77511	rc.dyndns.update: Dynamic DNS () There was an error trying to determine the public IP for interface - wan (pppoe0 ).
          S 1 Reply Last reply Reply Quote 0
          • S
            SteveITS Galactic Empire @Vertex
            last edited by

            Are you all using the new PPPoE? (Try both)

            If you can find a common link, someone should make a bug report at redmine.pfSense.org.

            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!

            V 1 Reply Last reply Reply Quote 0
            • V
              Vertex @SteveITS
              last edited by

              @SteveITS said in DynDNS is broken after 2.8 update:

              Are you all using the new PPPoE? (Try both)

              If you can find a common link, someone should make a bug report at redmine.pfSense.org.

              I have tested the old and now the new PPPoE, both does not work.

              1 Reply Last reply Reply Quote 0
              • F
                fyshed
                last edited by

                Found the fix via response on reddit. Gateway can't be offline so I needed to add an external monitoring address as I guess my ISP blocks ICMP traffic. Did that and dynamic dns started working again. System -> Routing -> Gateways.

                S 1 Reply Last reply Reply Quote 1
                • S
                  sunni @fyshed
                  last edited by

                  @fyshed Thx. Disabling gateway monitoring in System -> Routing -> Gateways fixed the issue for my case.

                  I'm using PPPoE with an external DSL Modem.

                  V H 2 Replies Last reply Reply Quote 0
                  • V
                    Vertex @sunni
                    last edited by

                    @sunni said in DynDNS is broken after 2.8 update:

                    @fyshed Thx. Disabling gateway monitoring in System -> Routing -> Gateways fixed the issue for my case.

                    I'm using PPPoE with an external DSL Modem.

                    You're right, it solved the issue for me immediately, too. Thank you for the tip!

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

                      I think I found an issue with the Dynamic DNS code. I wrote about my findings in this post:

                      https://forum.netgate.com/post/1217413

                      I'm wondering if it's the same issue for you all. In your logs do you also see this error?

                       Curl error occurred: Could not resolve host: <YOUR DDNS API HOSTNAME>

                      Are you trying to update a AAAA record? The issue I found is specific to Dynamic DNS with IPv6.

                      V 1 Reply Last reply Reply Quote 0
                      • V
                        Vertex @michael7786
                        last edited by

                        @michael7786 said in DynDNS is broken after 2.8 update:

                        I think I found an issue with the Dynamic DNS code. I wrote about my findings in this post:

                        https://forum.netgate.com/post/1217413

                        I'm wondering if it's the same issue for you all. In your logs do you also see this error?

                         Curl error occurred: Could not resolve host: <YOUR DDNS API HOSTNAME>

                        Are you trying to update a AAAA record? The issue I found is specific to Dynamic DNS with IPv6.

                        I only updated the A record, so the curl error was not present in my logs.

                        1 Reply Last reply Reply Quote 0
                        • H
                          horost @sunni
                          last edited by

                          @sunni Had the same issue with 2.8.0 I'm guessing since the Comcast-provided gateway IP is not pingable. Seems to be working fine again after disabling gateway monitoring as a workaround.

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