DDNS-Route53

DDNS-Route53 is a dynamic DNS application for Amazon Route 53, which is a dependable DNS web service.

  • Network Services
  • Tools & Utilities
DDNS-Route53 is a dynamic DNS application for Amazon Route 53, which is a dependable DNS web service. It updates IP addresses on a time-based schedule.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

32/100 Low

Maintained
0last commit 1795 days ago
Popular
3986 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
85no serious findings, CI

Based on 4 of 5 factors.

Availability: platform listings confirmed today, links checked 53 days ago

GitHub stars
86
Open issues
1
Last commit
2021-12-22
Latest release
v2.1.0
License
Unlicense
Activity
stale

Checked 21 days ago - source: GitHub (mthssdrbrg/ddns-route53)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set DOMAINS and IP providers Put your domain name(s) in DOMAINS and tell the container where to read your current IPv4/IPv6 address with IP4_PROVIDER/IP6_PROVIDER. Without these, the app has no domain to update and no address to send. source
  • Start it with the compose command Run docker-compose pull and docker-compose up --detach --build cloudflare-ddns to download the image and keep the updater running in the background. If you skip this, the app is not actually running to update DNS. source
  • Set PROXIED for proxied Cloudflare domains If your domains use Cloudflare's proxy (the orange cloud), set PROXIED with an expression such as is(yourdomain.com) so the updater sets proxying correctly. Without it, proxied DNS records may not behave as expected. source
  • AWS IAM policy & dependencies Install bash, awscli, and dig, then attach an IAM policy allowing Route 53 record changes to an AWS user or role. source

Fetched 37 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Which IAM permissions does ddns-route53 need to update Route 53?

Apply an IAM policy allowing route53:ChangeResourceRecordSets and route53:ListResourceRecordSets on the hosted zone. The source notes that limiting this to one record is not yet possible, though a sub-hosted zone can narrow the scope.

Do I need to expose a port or put it behind a reverse proxy?

No, it is a command-line updater script that changes Route 53 records. No web UI, port, or reverse-proxy setup is described.

Can it run a local script when the DNS record changes?

Yes, set DDNS_ROUTE53_SCRIPT to the path of a script to execute on changes.

Where does it get the current IP address?

It uses OpenDNS to get the current IP address.

What record type and TTL does the basic command assume?

The basic command assumes an A-type record and a TTL of 300 seconds, with AWS CLI credentials already set.

Answers sourced from github.com

Community

Collected 53 days ago - public community threads