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

    DDNS force update periodically

    Scheduled Pinned Locked Moved General pfSense Questions
    4 Posts 4 Posters 500 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.
    • departyD
      departy
      last edited by

      Hello,
      Is there a way to force the Dynamic DNS client periodically (once a day)?
      It would appear that the only way to do this is to change the IP address bound to the monitored interface.

      My question very specifically is, is it possible to force an update WITHOUT changing the interface address?

      I have a remote installation where I want to configure the DDNS client, and currently the DNS server currently has the WRONG address, so I am locked out of my other house until I visit it myself and force update it on site.

      Thanks in advance!

      Bob.DigB GertjanG 2 Replies Last reply Reply Quote 0
      • S
        serbus
        last edited by

        Hello!

        Some variation of this might work.

        John

        Lex parsimoniae

        1 Reply Last reply Reply Quote 1
        • Bob.DigB
          Bob.Dig LAYER 8 @departy
          last edited by

          @departy install the cron package. Then duplicate the dyndns job and configure it to your liking.

          Capture.PNG

          1 Reply Last reply Reply Quote 1
          • GertjanG
            Gertjan @departy
            last edited by

            @departy

            As @Bob-Dig :

            5a3455e9-33b1-4940-9361-46c08720ffb0-image.png

            says that dyndns is synced every day at 1AM1.

            The sync is also triggered at a WAN NIC network event, as this might imply a WAN IP change.

            If pfSense uses a RFC1918 IP on it's WAN, there must be an upstream router. These routers can renegotiate a new WAN IP without pfSense knowing about it. For pfSense, the RFC1918 didn't change : no WAN NIC event : the dyndns sub system isn't made aware of a possible change.
            As proposed : accelerate the checks.

            The dyndns script checks the domain DNS IP (it does a nslookup or dig) and compares the obtained IP with the IP stored in a local cache file. They must be the same. If so, the IP is shown on green in the widghet.
            If not, the IP is update on the DNS server side, and if all ok, then the local cache file is updated.

            No "help me" PM's please. Use the forum, the community will thank you.
            Edit : and where are the logs ??

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