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

    Dynamic DNS do not retry after failure

    Scheduled Pinned Locked Moved General pfSense Questions
    6 Posts 4 Posters 1.2k 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.
    • G
      gkri
      last edited by

      My ISP change my IP every day.
      I use Dynamic DNS with Dyn.com in order to update about 30 host on every WAN's  IP change.

      Usually all works perfectly, but in the last 2 months, some times 1 or 2 host have an error when updating.

      Jul 21 05:00:20 php-fpm[23501]: /rc.newwanip: Curl error occurred: Unknown SSL protocol error in connection to members.dyndns.org:443

      This happen some days other not, wit 1 or 2 host of more than 30.

      The problem is that the Dynamic DNS service do not retry to update this host after failure.

      Exist a way to make the Dynamic DNS service to check on regular basis if the cached IP is different for WAN's IP?

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

        What version of pfsense?

        Capitalism, currently The World's best Entertainment Control System and YOU cant buy it! But you can buy this, or some of this or some of these

        Asch Conformity, mainly the blind leading the blind.

        1 Reply Last reply Reply Quote 0
        • G
          gkri
          last edited by

          2.2.3 running on APU board.

          1 Reply Last reply Reply Quote 0
          • P
            phil.davis
            last edited by

            As a workaround you can install the Cron package and use it to edit the Cron job that runs once a day to check the dynamic DNS entries. If you run that more frequently then it is going to try to update any entries that did not update the first time.

            As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
            If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

            1 Reply Last reply Reply Quote 0
            • C
              cmb
              last edited by

              That appears to be a result of sending a lot of requests to Dyn, they reject some of the connections (probably rate limiting because of abuse issues).

              Putting it in cron as Phil mentioned is an option. Might want to contact Dyn support and see if they have any suggestions. You're paying for those hostnames, you ought to be able to update them all at once. There may be another option with Dyn, like updating one FQDN, and having the rest as CNAMEs back to the one you're updating.

              1 Reply Last reply Reply Quote 0
              • G
                gkri
                last edited by

                Thanks!!!

                I will be contacting Dyn.com

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