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

    Cannot get DDNS working on my Dual WAN failover setup.

    Scheduled Pinned Locked Moved Routing and Multi WAN
    1 Posts 1 Posters 307 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.
    • l3radyL
      l3rady
      last edited by

      I'm running pfSense 2.5.2-RELEASE.

      I have one pfSense router that I cannot get DDNS to work for the life of me. I've tried both Cloudflare and route53 DDNS clients and they both fail with an error like:

      Dec 22 16:31:39	php-fpm	348	/services_dyndns.php: Curl error occurred: Could not resolve host: route53.amazonaws.com
      

      Looking at the logs it works out the correct public IP but for whatever reason when it goes to the client API to send the IP the curl request fails. I have similar setups elsewhere and they all work fine with the same configuration.

      When I click save on the DDNS settings it takes over a minute to save as it attempts to update the DDNS. It seems that it does try to make the connection to the API but then times out after 60s.

      If I run curl https://route53.amazonaws.com from the command line it returns expected data. Pings, traceroutes, and general web browsing all function correctly.

      My WAN setup is as follows:

      Screenshot 2021-12-22 at 17.02.38.png

      I have a gateway group set up as failover:

      Screenshot 2021-12-22 at 17.04.01.png

      And my default gateway set as the failover:

      Screenshot 2021-12-22 at 17.04.23.png

      My DDNS settings monitor the failover group:

      Screenshot 2021-12-22 at 17.13.52.png

      My DNS settings are as follows:

      Screenshot 2021-12-22 at 17.23.12.png

      Firewall rules are set as a default install bar adding a LAN anywhere rule and allowing the two WAN interfaces to be pinged for outside monitoring. Outbound NAT rules are auto.

      Everything is configured as bog-standard but for the life of me cannot work out why DDNS won't work.

      What can I do to further diagnose the issue to find where the problem might lie?

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