What is DNS management?
DNS management is primarily located in the Hetzner Console.
In the konsoleH, you can also manage access to your zone files or change your nameservers.
For comprehensive documentation on our DNS and the options available for DNS management, see DNS.
DNS management
Reset zone
This function restores your DNS entries to the original state of the default zone. Any changes made previously will be lost as a result.
Delete zone
This function deletes the DNS zone for the selected domain. All DNS entries will be deleted as a result and the domain will no longer be accessible.
Note that it can take up to 24 hours for the changes to take effect worldwide (DNS propagation).
DNS Authorisation
konsoleH can assist you with the administration of your domain by automatically making necessary changes to your zone file (e.g. for subdomains, SSL certificates, etc.).
Responsible DNS servers
This section shows you which nameservers are currently responsible for resolving your domain’s name. If your domain is managed via konsoleH, you can change the nameservers registered for your domain here. Please note that for some top-level domains, changes must be made manually. These are carried out exclusively during our standard support hours and may therefore take some time.
⚠️ If your domain is not registered with Hetzner, you cannot change the DNS servers via konsoleH.
Change nameservers
This function allows you to change the nameservers for your domain. It is NOT sufficient to simply change the NS records in your zone.
Change nameservers
This function allows you to update your nameservers directly at the registry. Important note: it is NOT enough to simply change the NS records in your zone file.
Please note the following:
- You must insert at least 2 new DNS servers.
- Mixing our standard DNS servers with external DNS servers is not possible.
- The domain must be correctly set up on the DNS servers.
- As soon as you choose to use external DNS servers, the settings in our DNS administration will not be relevant anymore!
- Please take note of the DNS propagation time (up to 24 hours).
- Some domain registration authorities additionally check the DNS servers before the update. Invalid settings aren't saved in this case.
Some top level domains do not support automatic nameserver updates. These updates will only be processed during our normal support hours and may take some time.
Managing DNS records for managed servers
For managed servers, you can click on the hosting name → DNS Management → DNS Records to manage all domains on the server.
Important entries for web hosting and managed servers
A and AAAA records
A and AAAA records are responsible for resolving your domain to the relevant IP for your managed server. You can find both the A and AAAA records on konsoleH by going to Details > Hosting Server. Please check that you have correctly set the A and AAAA records so that your domain will be reachable via both IPv4 and IPv6.
; A records
@ IN A <IPv4 for the hosting server>
www IN A <IPv4 for the hosting server>
; AAAA records
@ IN AAAA <IPv6 for the hosting server>
www IN AAAA <IPv6 for the hosting server>MX
The MX record is responsible for delivering and sending your mails and should always point to the relevant mail server. If you would like to send mails via our server, then the MX record needs to point to your hosting server's name.
; MX records
@ IN MX 10 <server name>.your-server.de.⚠️ Please make sure that the target domain has a "." after the top-level-domain at the end.
CNAME
A CNAME is a DNS entry that is used to create an alias connection from one domain name to another one. Like the MX record, the CNAME record points to a domain that already exists. This is a good thing because it means that you do not need to enter IP addresses and other records twice. However, the CNAME is not a redirect. By default, this CNAME record is already configured for web hosting and managed server customers. It must be set like this if you want to use our mail system.
; CNAME records
autoconfig IN CNAME mail.your-server.de.⚠️ Please make sure that the target domain has a "." after the top-level-domain at the end.