DNS Management

DNS management is a service for those who want to be able to change the DNS records of their domain.

Features: Add, remove, modify entries of types A (Internet v4 address), AAAA (Internet v6 address), CNAME (canonical name), DNAME (delegated name), NS (name server), MX (mail server), TXT (text entry), SRV (network service), PTR (reverse entry) and other types.

DNS MANAGEMENT ON TUTHOST

After ordering the service – in order to be able to manage DNS records of domains – you need to forward the domain to special nemservers:

• park1.tuthost.com
• park2.tuthost.com

After that you will be able to change the following record types in the control panel:

Type A records (Internet v4 address)

Both of these entries direct the host (domain or subdomain) to the IP address. The “A” entries are used to bind the host to an IPv4 IP address and the “AAAA” entries are used to point to an IPv6 address.

The standard format of these entries:

host IN A IPv4_address
host IN AAAA IPv6_address

AAAA (Internet v6 address)

AAAA records are used for IPv6 addresses and work the same way as A records. The only difference is that A records are used for IPv4 addresses, while AAAA records are used for IPv6 addresses.

CNAME (canonical name) records

CNAME records work as aliases for normal records on your server (which are specified in A or AAAA records).

For example, we may have A record, with host “server1” and a record “www” specified as an alias for that host:

server1 IN A 111.111.111.111
www IN CNAME server1

In this case, when accessing the www host, it will read the IP address of server1 and send a request to it.

DNAME (delegated name)

DNAME records are used to forward all names in a domain to another domain.

Distinguished from CNAME records, which can only send one subdomain (host) from a domain. This record may be needed when the company moves to another domain, and CNAME record is a lot, so not to create them all in the new domain, it is enough to create a DNAME record.

NS (name server)

This type of record defines the nemservers that are used for this zone.

You may wonder, “if the zone file is already on the nameserver, why would it reference itself?” One of the things that makes DNS technology stable is multi-level caching. One of the reasons you might need this entry is if the zone file comes from a cached copy or another nameserver. There are other reasons, but we will not discuss them now.

The record looks about the same as the MX

IN NS ns1.domain.com.
IN NS ns2.domain.com.

MX (mail server)

MX records are used to tell mail servers that send mail to your domain which server will handle the mail. In most cases, if you keep both hosting and mail on the same server, you do not need to make any changes to this entry. But there are times when, for example, the site is located on one hosting service, and to work with the mail you want to use another service (eg gmail) is for such cases and need MX record.

Unlike other record types, the MX record applies to the entire domain at once. An entry might look something like this:

IN MX 10 mail.domain.com.

TXT (text entry)

TXT records are used to store any text information that is easy to retrieve. Most often TXT records are used to store SPF data and confirm the domain owner. Also in this entry is often stored DKIM data.

SRV (network service)

An SRV entry directs one domain to another, using a specific port. It allows special services such as VOIP or IM to be directed to another domain.

An example of such an entry:

_http._tcp.example.com. SRV 0 0 80. www.example.com.

This entry contains the following data:

• The service name is _http
• Protocol – _tcp
• Host – example.com.
• Priority – Works just like priorities in MX. The smaller the number, the higher the priority, 0 is the maximum priority.
• Weight – allows the server administrator to distribute the load to different targets. 0 is the lowest load.
• Port – the actual port on which the service is running.
• Host – to which this service is routed

PTR (reverse recording)

PTR records are used to determine the name associated with an IP address. PTR records are inverse to A or AAAA records, that is, if A record connects a domain with an IP address, then PTR record connects IP address with a domain.

An example of such an entry:

444.333.222.111.in-addr.arpa. 33692 IN PTR host.example.com.