How to Get Started with dynv6

Updated

You can get started with dynv6 by signing up, then either choosing a free hostname under a dynv6-managed domain or delegating your own domain to dynv6. It is a free dynamic DNS service for IPv4 and IPv6 addresses, and it is explicitly not intended for critical services because it does not offer enterprise-grade DDoS protection or SLAs.

What dynv6 does

dynv6 gives public hostnames to dynamic IPv4 and IPv6 addresses. The main use case is reaching private hosts without setting up NAT and port forwarding.

For IPv6, dynv6 combines a dynamic IPv6 prefix with a host identifier such as a MAC address or Host ID. The site gives this example:

2001:1234::/64 + 00:80:41:ae:fd:7e = 2001:1234::280:41ff:feae:fd7e

That means your host keeps a stable public hostname even when the network prefix changes.

Getting started

  1. Sign up or sign in. The site provides Sign up and Sign in links. After signing in, you manage your zones and domains from the My Zones and My Domains areas.
  2. Choose how to get a hostname. You have two options:
    • Pick a free hostname to start.
    • Delegate your own domain to dynv6.
  3. Configure the zone. Use the documentation and the available update methods to connect your host or router to dynv6.
  4. Verify the update. Once your client sends an address update, check that the hostname resolves to the expected IPv4 or IPv6 address.

Update methods

dynv6 offers several ways to update your zones:

  • REST API
  • Update API
  • DynDNS API
  • SSH with public key authentication
  • DNS updates with TSIG keys

Webhooks can also be used to update external services whenever your IP address changes.

Which method to use depends on what your router or host supports. If your device has a built-in DynDNS client, the DynDNS API is usually the simplest fit. If you manage DNS yourself, TSIG-based DNS updates or the REST API may be more appropriate.

When dynv6 is a good fit

dynv6 is suitable for:

  • Reaching private hosts from outside your network without NAT or port forwarding
  • Dynamic IPv4 and IPv6 addresses that need a stable public hostname
  • Users who want free hostnames or want to delegate their own domain
  • Setups that can use one of the supported update methods

dynv6 is not suitable for:

  • Critical services
  • Situations that require enterprise-grade DDoS protection
  • Situations that require SLAs

The site states these limitations directly, so plan accordingly if uptime guarantees matter to you.

Next steps

After signing up, start with a free hostname to test the update flow. Once that works, you can delegate your own domain or move to a more automated update method such as the REST API, DynDNS API, or webhooks.