Dynway
Dynamic DNS for homes, offices, labs, and small servers — keep a stable dynway.eu hostname even when the public IPv4 or IPv6 address changes.
What it is
Dynway is WAYSCloud Dynamic DNS. It gives you a stable hostname under dynway.eu for networks where the public IPv4 or IPv6 address can change.
Use it for a home router, office network, lab server, camera gateway, VPN endpoint, or any small self-hosted service that needs to stay reachable without a fixed IP address. Your router or client updates the hostname through the standard DynDNS2 protocol, and WAYSCloud keeps the DNS A and AAAA records pointed at the latest public addresses.
When to use
Use this when you need:
- Remote access to a home or office network with a changing public IPv4 or IPv6 address
- VPN endpoints that need a stable hostname instead of a fixed IP
- Small self-hosted services, lab servers, or camera gateways behind a router
- Routers that already support DynDNS-compatible custom providers
- Simple DNS automation without running your own update service
When NOT to use:
- Authoritative DNS zone management — use DNS Management
- Production workloads that require a fixed IP address — use VPS
- Private service discovery inside an application — use your application platform or service registry
How it works
Dynway separates setup from runtime updates:
- Create a Dynway name such as
home.dynway.eu - Create a router token for that name and save the password once
- Configure your router or DynDNS client to call
https://dynupdate.wayscloud.services/nic/update - When your public IPv4 or IPv6 address changes, the router sends an update and Dynway points the matching DNS record at the new address
IPv4 updates write the A record, while IPv6 updates write the AAAA record. Most routers can use Dynway as a custom Dynamic DNS provider because the update endpoint follows the DynDNS2 response format.
Features
Dynway is designed to be small, predictable, and compatible with existing router firmware.
Stable hostnames
- Customer-owned hostnames under
dynway.eu - One live Dynway name per customer in the first version
- Current IPv4 and IPv6 state, last update, last seen, and update count visible through the API
Router compatibility
- DynDNS2-compatible
/nic/updateendpoint - Works with routers and clients that support custom Dynamic DNS providers
- Optional
myipparameter for public IPv4 or IPv6; Dynway can fall back to the address seen by the update endpoint
Credential control
- Router tokens are bound to one Dynway name
- Passwords are shown once when created or rotated
- Token rotation and revocation without deleting the hostname
Getting started
All Dynway functionality is available via the WAYSCloud API.
Create Dynway name
Create one customer-owned hostname under dynway.eu. In v1 each customer can have one live name. Requires dyn:write scope.
curl -X POST https://api.wayscloud.services/v1/dyn/names \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "home"
}'Create router token
Issue the first active router token for a Dynway name. The router password is returned once and cannot be retrieved later.
curl -X POST https://api.wayscloud.services/v1/dyn/names/{name}/tokens \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"description": "home-router"
}'List Dynway names
List the customer-owned Dynway hostnames that can be updated by routers or small servers. Each name is a stable *.dynway.eu hostname with current IPv4/IPv6 state, update timestamps, and active router token metadata. Requires dyn:read scope; dyn:write implies read.
curl https://api.wayscloud.services/v1/dyn/names \
-H "X-API-Key: YOUR_API_KEY"List router tokens
List router token metadata for a Dynway name. Token passwords are never returned after creation.
curl https://api.wayscloud.services/v1/dyn/names/{name}/tokens \
-H "X-API-Key: YOUR_API_KEY"See all 9 endpoints in the Dynway API reference.
Limits and quotas
Limits and quotas depend on the selected plan and region. See the dashboard or API for current constraints.