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

    Dynamic DNS on Route53

    Scheduled Pinned Locked Moved DHCP and DNS
    2 Posts 2 Posters 440 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.
    • D
      depam
      last edited by

      Hello,

      Just trying to integrate DynamicDNS with my existing Route53 zone.
      I have added IAM policy and API access. It looks good and I can see that pfsense created IN A record on my Route53.
      However, I am curious how to test this so I changed the record to Route53 itself by changing IP address and tried to edit and save and update option on Pfsense and it doesn't seem to update the record.

      Does this mean that the record will only be updated when WAN IP changes? Appreciate if you can share your experience if it does as expected. Thanks in advance.

      1 Reply Last reply Reply Quote 0
      • D
        dgilmour77
        last edited by dgilmour77

        Route 53 DDNS update have stopped working for me too Here is a post I made on Reddit r/PFSENSE. I got no replies there, so posting here as a reply in the hope that this will be worthy of someone's attention.

        =====

        When doing DDNS updates, the log says:

        Jun 21 00:37:42 	php-fpm 	703 	/services_dyndns_edit.php: Curl error occurred: Failed to connect to route53.amazonaws.com port 443: Operation timed out
        Jun 21 00:37:42 	php-fpm 	703 	/services_dyndns_edit.php: Dynamic DNS route53 (xxx.xxx.net): _checkStatus() starting.
        

        To debug this, I noticed that earlier in the log, it showed the URL it was going to use for the update:

        Jun 21 00:36:27 	php-fpm 	703 	/services_dyndns_edit.php: Sending request to: https://route53.amazonaws.com/2013-04-01/hostedzone/--zoneID--/rrset
        

        So I tried a curl to that url from the pfSense command line -- worked fine. So no idea why the connect is failing. Incidentally, I have no IPv6 enabled on the box. The aws log shows the last successful update was about 45 days ago, I think when I was still on 2.4.4 which is why I'm worried this might be a 2.4.5 or 2.4.5-p1 bug.

        UPDATE:
        This appears to be related to routing, please see further info in the related post just made in the routing area

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