Appearance

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. Dynway is managed through the same WAYSCloud account and customer portal as the rest of the platform.

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:

  1. Create a Dynway name such as home.dynway.eu
  2. Create a router token for that name and save the password once
  3. Configure your router or DynDNS client to call https://dynupdate.wayscloud.services/nic/update
  4. 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. Business accounts can also label names by site, monitor expected check-ins, and receive signed webhook events without operating a separate DNS update service.

Features ​

Dynway is designed to be small, predictable, and compatible with existing router firmware. Home Free and Business Fleet are selected from the existing WAYSCloud account type; Dynway does not create a second account identity.

Stable hostnames ​

  • Customer-owned hostnames under dynway.eu
  • Home Free includes one live name; Business Fleet receives a plan-aware site quota
  • Current IPv4 and IPv6 state, last update, last seen, and update count visible through the API

Router compatibility ​

  • DynDNS2-compatible /nic/update endpoint
  • Works with routers and clients that support custom Dynamic DNS providers
  • Optional myip parameter 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

Business Fleet operations ​

  • Per-name labels, site codes, tags, and optional liveness monitoring
  • Current online, late, offline, and recovery status with retained event history
  • An authoritative A/AAAA DNS check every five minutes, with an explicit drift flag and last successful check time
  • Signed HTTPS webhooks for selected update, monitoring, DNS-drift, and recovery events

Authoritative DNS monitoring ​

Business Fleet independently checks the published A and AAAA records against the most recent Dynway state. This makes a router check-in and published DNS integrity visible as separate signals.

When an authoritative answer does not match, Dynway raises a dns_drift status and a dyn.name.dns_drift event. If another operational problem is already active, the drift flag stays visible without hiding that condition. Once the published records match again, the flag clears and Dynway emits dyn.name.recovered when the name is online.

The API exposes dns_drift_detected and dns_checked_at. A missing dns_checked_at means an authoritative check has not completed yet; it is not a router failure.

Getting started ​

All Dynway functionality is available via the WAYSCloud API.

Create Dynway webhook endpoint ​

Create one Business Fleet webhook endpoint for selected Dynway event types. Targets must use HTTPS and resolve only to public addresses. The HMAC signing secret is returned exactly once, is kept in Vault, and is never stored in maindb. Requires active Dynway service and dyn:write.

bash
curl -X POST https://api.wayscloud.services/v1/dyn/webhook-endpoints \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "name": "NOC receiver",
  "url": "https://hooks.example.com/dynway",
  "event_types": [
    "dyn.update.good",
    "dyn.name.offline",
    "dyn.name.dns_drift",
    "dyn.name.recovered"
  ],
  "is_active": true
}'

Create Dynway name ​

Create one customer-owned hostname under dynway.eu within the authenticated customer's Home Free or Business Fleet quota. Requires dyn:write scope.

bash
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.

bash
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 webhook endpoints ​

List webhook endpoints owned by the authenticated Business Fleet customer. Endpoint configuration is customer-scoped; signing secrets and Vault references are never returned. Requires dyn:read.

bash
curl https://api.wayscloud.services/v1/dyn/webhook-endpoints \
  -H "X-API-Key: YOUR_API_KEY"

List Dynway webhook deliveries ​

List customer-owned Business Fleet webhook delivery diagnostics in descending creation order. It returns bounded response samples and sanitized errors, but never callback payloads, signing secrets, or Vault references. Requires dyn:read.

bash
curl https://api.wayscloud.services/v1/dyn/webhook-deliveries \
  -H "X-API-Key: YOUR_API_KEY"

See 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.

Open Dynway in dashboard