Create and manage DynDNS domains
A DynDNS domain at IPv64.net is a fixed name such as yourdomain.ipv64.net that always points to the current IP address of your connection. This page shows how to create the domain, which domain suffixes are available, how to set up DNS records, wildcard and IPv6 prefix, and where to find the domain key.
Create a domain
After logging in, you create a free DynDNS domain at ipv64.net/dyndns. The free account allows up to 3 DynDNS domains; the numbers for the other account classes are listed under Account & limits.
- Choose a name
Enter your desired name in the Add DynDNS address card, e.g.homelab001. - Choose a domain suffix
Pick one of the 19 domain suffixes next to it. The default is.ipv64.de. - Create
Click Create domain NOW. The domain is active right away. IPv64.net sets the most important DNS settings automatically.
These rules apply to the name:
- 3 to 64 characters: lowercase letters, digits and hyphen. Uppercase letters are converted to lowercase automatically.
- Each name can be taken only once per domain suffix. Some names and words are blocked.
Possible messages when creating a domain:
| Message | Meaning |
|---|---|
Domain was successfully created. | The domain has been created. |
The domain name is already taken. | The name is already taken under this suffix. |
Domain contains non-permitted characters. Minimum 3 and maximum 64 characters. | Invalid characters, too short, too long or a blocked name. |
Your domain limit has been reached. | The domain limit of your account class has been reached. |
Without logging in, you can use Check Domainname on ipv64.net/dyndns to see under which suffixes your desired name is still available.
Then enter the update URL in your router or a script, see Routers & devices. Domains can also be created via the API.
Available domain suffixes
You can create your DynDNS subdomain under these 19 domains:
ipv64.net | ipv64.de | any64.de | api64.de |
dns64.de | dyndns64.de | dynipv6.de | eth64.de |
home64.de | iot64.de | lan64.de | nas64.de |
root64.de | route64.de | srv64.de | tcp64.de |
udp64.de | vpn64.de | wan64.de |
All suffixes work the same way. If you want to use your own domain, read Own domain.
Domain overview
The DynDNS-Domain Overview card lists all your IPv64 domains with their record types, the time of the last update and the status.
| Display | Meaning |
|---|---|
Active | The domain is active. |
Deactivated | The domain is deactivated. Updates are then rejected with badauth. |
No A Record | The domain has no records yet. |
FO, FO/AFB, MFO | A record of the domain is protected by DNS failover (automatic, automatic with fallback, manual). |
| Let's Encrypt icon | There is a TXT record for the ACME challenge. |
CDN64 | At least one name of the domain is switched on in CDN64. |
The Do column offers for each domain:
- EDIT Domain: edit records, wildcard, IPv6 prefix and update URLs.
- Check DNS: DNS lookup of the domain.
- Open Domain in new Tab.
- Update the A-Record automatically: enters the IP address your browser is currently connected with – as an A record for IPv4, as an AAAA record for IPv6. The call is counted like a DynDNS update.
- DELETE the domain permanently, see Delete.
Create and edit DNS records
Via EDIT Domain you add further DNS records. Each record consists of prefix, type and target:
| Field | Content |
|---|---|
| Präfix | Name in front of your domain, e.g. nas for nas.yourdomain.ipv64.net. Empty = the domain itself. |
| Domain | Your domain (fixed). |
| TTL | Display only, see TTL. |
| Typ | A, AAAA, TXT, MX, NS, SRV, CNAME, TLSA or CAA. |
| Ziel | Content of the record, e.g. IP address or text. |
Create record saves the record. To change one, click Edit this Domain Record in the Domain Records table and then Edit entry. The type cannot be changed.
Record types and format
| Type | Purpose | Format in the “Ziel” field |
|---|---|---|
| A | IPv4 address of the target | 192.0.2.10 |
| AAAA | IPv6 address of the target | full address 2001:db8::10, interface ID only ::211:22ff:fe33:4455 or MAC address, see IPv6 prefix |
| CNAME | Alias to another name | target.example.com |
| MX | Mail server | mail.example.com or 10 mail.example.com (priority 10 if omitted) |
| TXT | Text, e.g. SPF, DKIM or Let's Encrypt | any text |
| NS | Delegation to another name server | ns.example.com |
| SRV | Port of a service | prefix _service._proto.name, target with four values 10 5 5060 sip.example.com (Priority Weight Port Target) |
| TLSA | Verify certificates (DANE) | prefix _service._proto.name, target with four values (CertUsage Selector Matching Cert) |
| CAA | Allowed certificate authorities | three values, e.g. 0 issue letsencrypt.org |
A CNAME cannot share a prefix with other records. If a prefix has a CNAME, the updater rejects a DynDNS update for this prefix with CNAME is set.
Prefixes (subdomains)
You can add as many prefixes as you like, e.g. nas.yourdomain.ipv64.net. Allowed are lowercase letters, digits, dot, hyphen and underscore. Multi-level prefixes such as a.b work, as does _acme-challenge for Let's Encrypt certificates (DNS challenge, e.g. with acme.sh or Certbot).
Status and actions per record
| Display | Meaning |
|---|---|
Valid | The record is fine. |
Not valid | A/AAAA without a valid IP address, or prefix and interface ID together have more than 8 groups. |
Updating.. | The record is being sent to the DNS server. |
Deactivated | The record is deactivated, e.g. during a failover, and cannot be edited then. |
CDN64 Active | Own A/AAAA record of a name in CDN64: it is dormant while CDN64 is switched on and the DynDNS updater keeps updating it. |
CDN64 Server | A/AAAA record of a CDN64 edge server. CDN64 manages it; it cannot be edited or deleted. |
| DNS Protected: the record belongs to a failover rule. | |
CGNAT, this will not work! – the IPv4 is in 100.64.0.0/10 (CG-NAT) and cannot be reached from outside. |
A and AAAA records also show (update URL for this record only, see Keys). Update Record in DNS Server sends a record to the DNS server again, deletes it after a confirmation.
Messages when saving:
| Message | Meaning |
|---|---|
DNS record already exists. | Exactly this record already exists. |
CNAME: Only one CNAME allowed per prefix.domainname. | The prefix already has a record. |
Invalid DNS record details. Please read FAQ. | The target does not match the type. |
The DNS server rejected this record … | Conflict with an existing record or invalid format. Details are under Logs. |
TTL
You do not set the TTL (time to live) yourself. It depends on your account class and is only displayed in the TTL field. The values per class are listed under Account & limits.
Wildcard
The option Set wildcard (*.) automatically? is switched on for new domains. IPv64.net then automatically adds a matching wildcard entry for every A, AAAA and CNAME record. So besides yourdomain.ipv64.net, anything.yourdomain.ipv64.net also points to your IP address.
- For DynDNS addresses this is usually the right choice.
- If you switch the option off in the domain settings, only
yourdomain.ipv64.netitself resolves. You can then set individual*records by hand. - A change is applied to all existing records immediately.
IPv6 prefix and interface ID
With IPv6, every device in your home network has its own public address. It consists of the prefix of your connection (the first 64 bits) and the fixed device part, the interface ID (the last 64 bits). If your provider changes the prefix, all addresses change. To keep your devices reachable by name anyway, you store the prefix at the domain and only the interface ID per device.
2001:db8:1234:5600:211:22ff:fe33:4455
└──── Prefix ────┘ └─ Interface ID ─┘
changes stays the same
- Save the prefix
Under EDIT Domain, enter the prefix with its length in the IPv6 Prefix (DynDNS Prefix) field, e.g.2001:db8:1234:5600::/64, and click Save IPv6 Prefix. The prefix must end with::/and the length. Alternatively, IPv6 Prefix autodetect openshttps://ipv6.ipv64.net/nic/update?key=YOUR_DOMAIN_KEY&ipv6prefix=auto&onlyprefixin a new tab and detects the prefix automatically, without changing any A or AAAA record. - Add devices
Add one AAAA record per device whose target contains only the interface ID and starts with::, e.g. prefixnas, target::211:22ff:fe33:4455. Instead of the interface ID you can also enter the device's MAC address, e.g.3C:49:37:12:26:B3. It is converted to the interface ID automatically (EUI-64), here::3e49:37ff:fe12:26b3. - Keep the prefix current
Let your router send the prefix with every update; all device records are then adjusted automatically. Ready-made URLs are under Example URLs for the IPv6 prefix, the FRITZ!Box URL under FRITZ!Box with IPv6 prefix.
Example: how the addresses are built
The prefix 2001:db8:1234:5600::/64 is stored at the domain yourdomain.ipv64.net:
| Prefix (record) | Target in the AAAA record | Address in DNS |
|---|---|---|
nas | ::211:22ff:fe33:4455 | 2001:db8:1234:5600:211:22ff:fe33:4455 |
printer | MAC 3C:49:37:12:26:B3 | 2001:db8:1234:5600:3e49:37ff:fe12:26b3 |
pi | ::10 | 2001:db8:1234:5600::10 |
camera | ::1:211:22ff:fe33:4455 | Not valid – more than 8 groups together |
If your provider assigns the prefix 2001:db8:abcd:7700::/64 tomorrow and your router reports it, nas.yourdomain.ipv64.net automatically becomes 2001:db8:abcd:7700:211:22ff:fe33:4455 – you change nothing on the record.
- The first 64 bits count. The length (
/56,/64…) is stored as well but does not change how the address is built.2001:db8:1234:5600::/56also results in addresses in2001:db8:1234:5600::/64. - Interface ID with at most 4 groups, so that prefix and interface ID add up to 8 groups.
- One prefix per domain. Devices in another /64 network of your connection (e.g. a guest network
2001:db8:1234:5601::/64) need a domain of their own with its own prefix, or an AAAA record with the full address.
In the record table, the stored prefix is shown in bold in front of the interface ID; with more than 8 groups it shows Not valid.
For records with an interface ID, the table shows no record update URL of their own (). They are updated via the prefix of the domain.
Ignore IPv4 or IPv6 (DS-Lite, CG-NAT)
With DS-Lite and CG-NAT you have no public IPv4 address of your own. The shared IPv4 of your provider cannot be reached from outside and should not be in the DNS. For this, EDIT Domain has the selection Ignore IPv4 / IPv6 on the updater (/nic/update)?:
| Setting | Effect on updates via /nic/update |
|---|---|
IPv4 & IPv6 accepted (default) | A and AAAA records are updated. |
Ignore IPv4 / A Records | Only the AAAA record is set – the right choice for DS-Lite and CG-NAT. |
Ignore IPv6 / AAAA Records | Only the A record is set. |
If you need a public IPv4 despite DS-Lite, the Cloud Router helps.
Domain key and update URLs
Under EDIT Domain, IPv64.net shows three update URLs with different scopes. The smaller the scope, the less can happen if a key falls into the wrong hands.
| Key | May change | Update URL |
|---|---|---|
| Record – Security Level 3 (High) | only the A or AAAA record of one prefix | https://ipv4.ipv64.net/nic/update?key=YOUR_RECORD_KEY (A) or https://ipv6.ipv64.net/nic/update?key=YOUR_RECORD_KEY (AAAA), at the record under |
| Domain – Security Level 2 (Mid), recommended | this one domain with all its prefixes | https://ipv64.net/nic/update?key=YOUR_DOMAIN_KEY |
| Account – Security Level 1 (Low) | all domains of your account | https://ipv64.net/nic/update?key=YOUR_ACCOUNT_KEY&domain=yourdomain.ipv64.net |
With the domain key, the domain parameter can be omitted. In routers and devices, use the domain key or the record key, not the account key.
The URLs are hidden at first. shows them, copies them, calls them directly.
Generate new domain update URL creates a new domain key (message New update hash key stored.). The old key is no longer valid – enter the new one in all routers and scripts. You renew the account key the same way in the Account Update URL row – this affects all domains of your account.
All parameters of the update URL and the updater's responses are described under Update URL & protocol. The API key for managing domains from scripts is explained under API.
Own domain
From a paid account class on, you can bring your own domain to IPv64.net and manage all its DNS records there, including DynDNS updates. The free account shows a note about an account upgrade instead. IPv64.net is not a registrar: you keep registering the domain with your provider.
- Add the domain
On ipv64.net/dyndns, click Add your own domain in the Add DynDNS address card, enter the domain (e.g.example.com) and click Eigene Domain JETZT hinzufügen. - Set the name servers
At your domain provider, enter the IPv64.net name servers:ns1.ipv64.netandns2.ipv64.net. - Check
The Your own Domains card showsNS OKin the NS Check column as soon as the IPv64.net name servers are in place.NS Badmeans other name servers still apply. This can take up to 48 hours.
After that you edit your own domain just like an IPv64 subdomain: records, prefixes, wildcard, IPv6 prefix and update URLs. How many own domains are possible depends on your account class.
Reset and delete a domain
Domain Reset
Domain Reset (at the top of the Domain Records card) immediately deletes all records of the domain and resets the entries in the DNS server. Use it if the domain no longer resolves correctly. After confirming with Reset domain NOW, you see Domain reset performed successfully. If errors persist, delete the domain and create it again.
Delete a domain
In the domain overview, DELETE the domain permanently deletes the domain with all its records after a confirmation (Confirm deletion → Delete). This cannot be undone.
Found a mistake or missing something? Tell us in the v64.tech forum. · Updated: 2026-10-29