Dynamic DNS
That is how your connection introduces itself today, and it goes away the day your address changes. Dynway gives you one you picked yourself — home.dynway.eu — and keeps it pointed at you through every change.
Home Free for private accounts. Business Fleet for teams that need visibility across sites.
Pick a name a person can actually say out loud. It follows your address across every change, and it does not expire — so you are never handed a fresh pile of consonants to memorise.
The protocol is the same either way. What differs is how many names you run, and how much you need to be able to prove afterwards.
Home lab, NAS, cameras, a VPN back to the house, a game server, the cabin.
dynway.eu that survives every reconnectAnd we watch the line. If your router stops checking in, we tell you. You find out from us, rather than from something that will not connect while you are away.
home.dynway.eu — points at the house, whatever the line is doing today.
Branch offices, edge gateways, mobile uplinks, customer-premise equipment, lab and test networks — anywhere a fleet of connections needs stable names.
dyn:read and dyn:write scopes on API accessHere the alert is the product. A site that stops reporting is a site you cannot reach, and you need to know that before the person standing in it picks up the phone.
oslo-gw.dynway.eu — and when that router is replaced, one token dies, not the fleet.
A fleet is not a longer list of hostnames. What an operations team needs is the layer above: knowing which sites are reporting, which have gone quiet, and why. That is what this is.
“The site is down” is not a diagnosis. These are distinct states with distinct fixes, and the status view names the one you have. Every one of them is derived from what the update protocol already tells us — nothing probes your line.
| router silent | No update received inside the expected window. The record still resolves — it is simply going stale. |
| authentication failing | The router is reporting, and being turned away. Usually a token rotated at one end only. |
| record mismatch | The published record no longer matches the address the router last reported. |
| IPv6 missing | The A record is current, the AAAA never arrived. Dual-stack that is quietly running on one leg. |
| line flapping | Not a fault — a warning. The address changed twenty times today. Nothing is broken, but each change is a window in which something could not reach you. |
branch, warehouse, lab or vpn instead of reading a list of hostnames and remembering which is which.Described in specifics rather than as “monitoring”, so you can tell whether it fits before you commit to it. Talk to us about pricing for your fleet size.
Dynway speaks DynDNS2, the same protocol most routers have shipped with for twenty years. If yours has a “custom” or “user-defined” DDNS provider, these are the four values it asks for.
Verified against FRITZ!Box, OpenWrt ddns-scripts and MikroTik RouterOS, plus anything that speaks generic DynDNS2. Read more in the documentation ↗
DynDNS2 replies in single words. Worth knowing which ones mean stop and which mean carry on, because your router will act on them without telling you.
| Reply | Meaning |
|---|---|
| good <ip> | The record now points at that address. |
| nochg <ip> | It already did. Nothing was written. |
| badauth | Token missing, wrong, inactive or blocked. |
| nohost | That hostname does not belong to this token. |
| notfqdn | Not a valid Dynway hostname. |
| abuse | Rate or bad-auth guard stepped in. |
| 911 | Our fault, not yours. Back off and retry. |
Why 911 and never badauth for our own faults. Several router firmwares treat repeated badauth as a reason to disable the DDNS entry entirely — a working setup goes quiet and the owner finds out days later. So when something breaks on our side, Dynway answers 911, the one code that tells a router to wait and try again.
Dynway is part of the WAYSCloud platform, so it lives behind the same account as everything else we run. Three steps, and your router is reporting.
Same door whether you are a household or a company — open Dynway in WAYSCloud and sign up. Onboarding asks for a payment card, because the account is the key to every service on the platform.
For home use, Dynway is free. The card is not charged for it, and nothing starts billing on its own. It sits there until the day you decide you want a server, a database or a mailbox to go with your hostname.
Once you are signed in, the service is listed as Dynway. Pick your hostname under dynway.eu, then issue a router token for it. The token password is shown exactly once — copy it before you close the dialog, because it cannot be retrieved afterwards.
Open the DDNS settings in your router, choose the custom or user-defined provider, and paste in the four values from the setup section. Save it, and the first update usually lands within seconds.
Already have a WAYSCloud account? Open Dynway →
Dynamic DNS sees every address your connection has ever had. That is a small file, and a revealing one. Here is exactly who holds it and what is in it.
WAYSCloud is a Norwegian company. Your account, your tokens and your service data sit on WAYSCloud's own infrastructure, under Norwegian and EEA law — not on infrastructure rented from a company answerable to another jurisdiction.
The address being published, when it last changed, how many updates a name has had, and when its router last reported in. That is the whole record. No profiling, no enrichment, no resale, and nothing handed to a third party.
Analytics is self-hosted and runs without cookies, so there is no consent banner because there is nothing to consent to. The fonts you are reading come from our own font service, not from a third-party CDN.
The dynway.eu zone is DNSSEC-signed, so a resolver can prove the answer it got is the answer we published. The nameservers carry our names, not a reseller's.
Dynamic DNS is old, and most of what is still running shows it. Names that expire unless you answer a monthly email. One shared password sitting in every router you own. No record of what changed.