WAYSCloud has launched Dynway, a European dynamic DNS service that keeps a chosen dynway.eu hostname pointed at a connection even when its public IP address changes.
Dynway combines three ways of working with the service: the established DynDNS2 protocol for routers and update clients, desktop applications for computers that cannot update through a router, and a documented API for automation and business integrations.
At home, that means a simple and dependable name for a router, NAS, VPN endpoint, camera gateway, game server or cabin connection. For businesses, Dynway adds the monitoring, history and automation needed to operate a fleet of branch routers, edge gateways and mobile uplinks.
A name that stays put
Most residential and many business internet connections do not include a fixed public IP address. When the provider changes that address, anything relying on it can become difficult to reach.
Dynway replaces the changing address with a stable name chosen by the customer, such as cabin.dynway.eu. A compatible router or Dynway Desktop keeps the corresponding DNS record current whenever the connection changes.
The service supports IPv4 and IPv6 independently through A and AAAA records. It uses the established DynDNS2 protocol already supported by many routers, including custom-provider configurations in FRITZ!Box, OpenWrt and MikroTik RouterOS. The dynway.eu zone is also DNSSEC-signed.
Free and simple for home use
Home Free is available at no charge for private WAYSCloud accounts and includes one live Dynway hostname.
The name remains active until the customer deletes it. There are no recurring confirmation emails that can cause a hostname to disappear simply because a message was missed.
Setup is deliberately small: choose a name, create a router token and enter the Dynway values in the router’s dynamic DNS settings. The router receives a credential bound specifically to that hostname—not the customer’s WAYSCloud account password. The token can be rotated or revoked later without changing the hostname.
A WAYSCloud account is required. The payment card requested during account onboarding is not charged for Dynway Home Free, and no paid service starts automatically.
Desktop apps for Windows, macOS and Linux
Not every router supports a custom dynamic DNS provider, and sometimes the user does not control the router at all. For those situations, Dynway Desktop performs the update directly from the computer.
The app signs in through the existing WAYSCloud account, lets the customer choose or create a Dynway name and keeps it updated in the background. It reacts to network changes and sleep or resume events, while IPv4 and IPv6 are updated independently.
For laptops, Dynway includes an additional safeguard: it does not silently republish a hostname from an unfamiliar network. Updates pause until the user approves that network, permits a single update or chooses to allow updates from any network.
Dynway Desktop is available for Windows, macOS and Linux. The Windows installer is signed by WAYSCloud AS, the macOS build is notarized by Apple, and checksums are published for the available downloads.
Simple in the portal, programmable through the API
Dynway can be managed visually through the WAYSCloud customer portal, but the same capabilities are also available through the documented WAYSCloud API.
Through the API, customers can create and retire Dynway names, inspect plan limits, issue or revoke router and desktop credentials, rotate tokens, read current IPv4 and IPv6 state, retrieve status and event history, and manage monitoring settings.
Business Fleet customers can also manage site labels, locations and tags, configure signed webhook endpoints, inspect delivery results and retry failed webhook deliveries.
API access is separated into dyn:read and dyn:write scopes and remains bound to the customer’s existing WAYSCloud account. Credentials returned during enrolment or rotation are shown once and cannot later be retrieved through the API.
This makes it possible to automate site onboarding, router replacement, credential rotation and monitoring integrations without scraping a dashboard or building a separate dynamic DNS control layer.
Together, Dynway exposes three complementary integration surfaces:
DynDNS2 for routers and update clients
REST APIs for management and automation
Signed webhooks for operational events
Business Fleet: from hostnames to operational visibility
Many dynamic DNS services stop once a record has been updated. Dynway Business Fleet starts there.
Business Fleet treats each connection as a named site rather than another row in a hostname list. Teams can add locations, site codes and tags, then view the current IPv4 and IPv6 state, the most recent check-in and the latest operational result for each site.
The current Business Fleet configuration supports up to 50 sites per account, 30 days of event history and up to five signed webhook endpoints.
Monitoring is derived from the updates routers already send and from authoritative DNS state. Dynway does not need to probe the customer’s network. The resulting status can distinguish between a site that is late or offline, an updater that is failing authentication and a published DNS record that no longer matches the latest reported state.
The retained event history can be filtered by site, event type and status. This gives operations teams a practical record for reconstructing changes, identifying recurring issues and understanding whether a problem originated with the connection, its credentials or the published DNS state.
Events can be delivered to existing monitoring, automation or CMDB systems through HMAC-signed webhooks. Delivery history, retries and secret rotation are included, allowing Dynway to update the tools a business already uses instead of becoming another isolated dashboard.
European by design, open by protocol
Dynway is operated by WAYSCloud AS, a Norwegian company governed by Norwegian law and European data-protection requirements. WAYSCloud operates its core infrastructure within the EEA, while customer relationship data is stored in Norway.
The product follows the same principle of making infrastructure behaviour visible and controllable. Credentials are scoped and revocable, customer-facing event history is sanitised, DNS responses are protected with DNSSEC, and the product website uses self-hosted, cookieless analytics rather than third-party advertising trackers.
European operation does not mean introducing a proprietary protocol. Dynway works with existing DynDNS2-compatible equipment, provides documented REST APIs and remains part of the same WAYSCloud identity and management model as the rest of the platform.
Available now
Dynway is available now.