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

    Dynamic DNS failing (not making?) automatic updates

    Scheduled Pinned Locked Moved DHCP and DNS
    1 Posts 1 Posters 174 Views 1 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.
    • R Offline
      rtadams89
      last edited by

      I have pfSense (2.5.2) with two WAN connections configured in an active-passive setup. I also have 3 Dynamic DNS Clients configured, one for each WAN link and one for the default gateway (which would change depending on which WAN was active). All three are updating Cloudflare. All three also work fine when I manually force an update from the edit screen.

      Occasionally, when I am in the webConfigurator looking at something else, I'll notice the Dynamic DNS status for the secondary WAN shows a Red "X" and has not been updated. If I force an update manually, it returns to green.

      I enabled the verbose logging and saved the logs from when the issue occurred. It seems to be when a failover/failback between the WAN links happens; I see the other 2 clients make updates, but this one doesn't even seem to try.

      Here are the logs: https://pastebin.com/uarA2hnj

      The first (chronologically, last in the log file) is me manually updating the "home-secondary" client successfully. After that you see some WAN switching events and successful attempts at updating the other two clients, but never see any mention of "home-secondary" again. It's like pfSense doesn't even try.

      Any idea why home-secondary isn't updating automatically?

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