Need a new way to keep your records in sync? Compare hosted relays, self-hosted updaters, and dynamic DNS services before you change your router.
DNS-O-Matic popularized this pattern: one client request, multiple configured services. See its API docs
Why compare now? DNS-O-Matic says it is no longer accepting new accounts. Existing users should check which services receive their updates and choose a path that covers those destinations.
The closest fit depends on whether you need to update several providers, run software yourself, or simply keep one hostname current.
Send one familiar DynDNS-style request to a hosted endpoint and route it to the DNS records you configure across providers.
Run a container or binary that checks your public IP and updates records at supported DNS providers on a schedule.
Get a free Duck DNS hostname and keep it pointed at your changing IP with its update API or install guides.
Use a Dynu subdomain or your own domain with Dynu’s dynamic DNS service, clients, and update methods.
Provider support, device compatibility, and pricing can change. Confirm the details with each service before switching.
“Dynamic DNS” covers several different jobs. Start with the way you want updates to flow.
One router update → several DNS providersLook at DNSbun’s hosted relay workflow or a self-hosted updater such as ddns-updater.
I want to run it myselfddns-updater is designed to run as your own container or binary.
I just need a dynamic hostnameDuck DNS and Dynu provide hosted DDNS with their own update methods.
Record your current destinations first. Then configure the replacement and test an update before relying on it.
See DNSbun’s migration guideList each DNS or IP service DNS-O-Matic currently updates, plus the hostname and record type.
Pick a relay for one inbound request or set up a self-hosted updater or direct provider client.
Update the server and credentials in your client, send a test update, and confirm the destination records.
Its account creation page says new accounts are no longer being accepted. If you already use DNS-O-Matic, review your current destinations and prepare a replacement before changing your router settings.
For a hosted one-update-to-many-destinations workflow, DNSbun is being built around the DNS-O-Matic/DynDNS-style request format. It is currently an early access waitlist. For an option you can run yourself, compare ddns-updater.
DNSbun accepts all.dnsomatic.com as a compatibility alias for its all-destinations target. You still need to change the update server and credentials; check your device’s configuration fields before migrating.
They are dynamic DNS services with their own update flows. If you need one router update to reach several separate DNS providers, choose a relay or configure a self-hosted updater for each destination.
DNSbun is being built for people who want the DNS-O-Matic style workflow with a modern, hosted relay. Join the waitlist for launch updates.
