To be able to edit the DNS or nameserver entries, you must first log into your customer menu.
Now select the desired domain for which you want to edit the name server entries. For each (main) domain, you will find the menu item "DNS settings" under "Hosting and DNS".
You can first try out what is possible. The changes are only saved when you click on "Save changes". So if you are not satisfied with the changes, you can simply close the browser window or tab and have not broken anything.
Normally a subdomain is identified by the *. entry for A and AAAA of the main domain. However, as soon as an entry of any TYPE is created for any subdomain, the *. entry, according to the RFC for name servers, is no longer responsible. The consequence is that the A and AAAA record must then be created manually in the DNS for each subdomain.
Add or edit entries
To create a new entry, click on the "Add new entry" button.
You can edit entries by clicking on the "Edit" button in the line of the desired entry.
In both cases, an input mask opens where you can enter all the data required for the entry and then accept it.
| Field name | Field description | Example: Name |
|---|---|---|
| Name | The name that determines where the entry should apply. | imap.domain.tld |
| Type | The type of entry. A different type must be selected depending on the purpose. | MX |
| TTL | This is the abbreviation for "Time to live" and defines how many seconds the entry may be cached. | 8600 |
| Value (RDATA) | Contains the actual information for the DNS entry. This value varies depending on the type. The different types. | 10 mail.domain.tld |
Depending on the type, the "Value" field is divided into appropriately categorized fields to make your life a little easier. You can find out more below in the descriptions of the individual types.
A- and AAAA
Probably the most frequently used types. The value of these entries contains the IPv4 or IPv6 address of the target server and tells the client, for example your web browser, at which address the server is located that is to deliver the website, for example.
| Name | Type | Value |
|---|---|---|
| ipv4.name-of-the-domain.com | A | 192.0.2.1 |
| ipv6.name-of-the-domain.com | AAAA | 2001:0db8:0000:0000:0000:0000:0000:0000 |
NS
With the help of an NS record, you can have certain areas of your domain processed by another name server. We use this entry for SSL certificates, for example, to enable validation for external domains without having to update a corresponding entry for the external domain every 60 days.
The content (value) of the NS entry must be a domain to be resolved. Please note that this domain must not point to a CNAME entry. If you would like to define several name servers for an entry, you can create additional entries with the same name.
| Name | Type | Value |
|---|---|---|
| _acme-challenge.name-of-the-domain.com | NS | ns1.name-of-the-domain.com |
| _acme-challenge.name-of-the-domain.com | NS | ns2.name-of-the-domain.com |
CAA
CAA is short for DNS Certification Authority Authorization. This entry is for your security, as you can use it to specify which certification authorities may issue a certificate for your domain. This is to prevent certificates from being incorrectly issued for your domain.
You must know the following values in order to use this entry.
Flag
You can leave this value at 0 for the time being. In future, this value can be used to allow certification authorities only if they support the corresponding tag. If you want to know more about this, read section 4.5 of RFC8659.
Tag
| Tag Name | Tag Description |
|---|---|
| issue | This tag is used to allow a certification authority to issue a certificate for your website. If no one should be authorized to do so, you can enter ";" as the value, for example. This prohibits all certification authorities from issuing a certificate for your domain. |
| issuewild | The same applies here as for issue, except that this tag relates to wildcard certificates, i.e. for the domain or subdomain and all subdomains. |
| iodef | This tag allows you to enter a contact person or contact page so that you can be informed if an error has occurred. You can enter both a domain and an e-mail. Example website: https://name-der-domain.de/ Example e-mail: kontakt(at)name-der-domain.de |
Value
You can derive the value from the tag. For issue and issuewild, enter the corresponding certification authority. For iodef, you can look at the examples in the table.
CNAME
A CNAME record is an alias to an existing address. This entry always refers to an existing A or AAAA record.
Please note that you may not combine a CNAME record on a subdomain with other records such as a TXT record.
| Name | Type | Value |
|---|---|---|
| name-of-the-domain.com | A | 192.0.2.1 |
| en.name-of-the-domain.com | CNAME | name-of-the-domain.com |
| en.name-of-the-domain.com | TXT | This is not allowed! |
MX
An MX record relates exclusively to the e-mail area. You use it to determine which server is responsible for receiving emails sent to your domain. You can store several mail servers so that you have a backup server in the event of a server failure and can still receive the email. The so-called priority determines which server is first in line. The entry with the lowest value is preferred.
| Name | Type | Priority | Value |
|---|---|---|---|
| name-of-the-domain.com | MX | 10 | mail.name-of-the-domain.com |
| name-of-the-domain.com | MX | 20 | mail-backup.name-of-the-domain.com |
| mail.name-of-the-domain.com | A | 192.0.2.1 | |
| mail-backup.name-of-the-domain.com | A | 192.0.2.15 |
SOA
SOA stands for Start of Authority and contains important information for managing the zone. This entry is used for the synchronization of the database, a so-called zone transfer. The SOA entry contains information that is used to control the zone transfer.
How is this entry structured?
| Name< | Description< | Example |
|---|---|---|
| authority-domain | The master for this zone. It determines to whom dynamic updates should be sent. | ns1.name-of-the-domain.com |
| hostmaster-email-address | The e-mail of the person responsible for the zone. For this to work, the "@" must be replaced by a "." and dots by "\.". | contact.name-of-the-domain.com |
| zone-serial-number | A kind of version number. The current date should be used here to avoid duplicate versions. <YEAR><MONTH><TAG><VERSION> | 2021070601 |
| refresh-time | The number of seconds after which the server should ask the master for the current SOA entry in order to recognize changes. | 7200 |
| retry-time | The number of seconds after which the master should attempt to repeat a query if the server was previously unavailable. | 900 |
| expire-time | The number of seconds after the secondary server should stop accepting requests for the zone if it does not respond. | 1209600 |
| negative caching TTL | The number of seconds for which a negative response, such as a call to a non-existent subdomain, should be cached. | 86400 |
SRV
An SRV entry can be used by applications to find out at which address and which port a specific service can be found.
For example, if you have set up an LDAP server, you can create an SRV entry that points to it. As with the MX entry, it is also possible to prioritize and weight the services if you have several LDAP servers and want to distribute the load.
The name of the entry is structured as follows: _Service._Protocol.Name. An LDAP server that relies on TCP would therefore be called _ldap._tcp.name-of-the-domain.com. Note the underscore that is used before the service and before the protocol. It is intended to prevent confusion with other entries.
The SRV entry has the following properties
| Name | Name Description | Example Example |
|---|---|---|
| Priority | The priority of the target server. The server with the lowest value is accessed first. If this is not available, the next highest is attempted to be reached and so on. | 10 |
| Weighting | A server selection mechanism. Entries with the same priority and different weighting can be used for high availability clusters, for example. If you only want to connect one server, you can use "0" as the weight so that the entry is easier for others to read. | 0 |
| Port | The port to which the service listens. | 389 |
| Destination (in the DNS module: value) | The target address of the server on which the service is running. If you want to indicate that a service is deliberately unavailable, you can enter "." here. | ldap.typo3muster.de |
TXT
TXT entries consist, as can be easily deduced, of any text content. Some services, such as certificate issuers or Microsoft services, use this entry for validation. In the e-mail sector, TXT entries are used to recognize SPAM, so-called SPF entries.
| Name | Type | Value |
|---|---|---|
| name-of-the-domain.com | TXT | Hello world |
F.A.Q.
How can I have several entries with the same type point to the same name?
This requirement arises, for example, when using SPF and DMARC in connection with TXT entries. For example, if you need several TXT entries on test.name-der-domain.de, you can easily create several entries and enter the same name several times.
A special feature is that all entries with the same name also require the same time to live. The DNS module does this for you automatically, so you don't have to worry about it.
Example: Name
| Name | Type | TTL | value |
|---|---|---|---|
| test.name-of-the-domain.com | TXT | 86400 | Hello world |
| test.name-of-the-domain.com | TXT | 86400 | And one more entry |
I have accidentally marked an entry as deleted, can I undo this?
As long as you have not yet saved the changes, you can reset the entry by clicking Delete again.
Which characters can I use in a TXT entry?
- a-z
- A-Z
- 0-9
- space
- ! " # $ % & ' ( ) * + , - / : ; < = > ? @ [ \ ] ^ _ ` { | } ~ .