Dynamic DNS
Most connections get a new public address whenever the line resets. Dynway gives you a name on dynway.eu that follows it — your router reports the change, and the DNS record is current within seconds.
The address above is what every site you visit already sees. It is the part that changes. The hostname is the part that does not — that is the whole of dynamic DNS, and the rest of this page is how you wire it up.
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 reconnecthome.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 accessoslo-gw.dynway.eu — and when that router is replaced, one token dies, not the fleet.
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.
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.
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 AS, org.nr. NO 833 735 462 MVA. 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.