Skip to main content
Add a resource record
Last update:

Add a resource record

For your information

We've released new version of DNS hosting (actual) and stop supporting and developing legacy. Domains and resource records in DNS hosting (legacy) continue to work, we will warn you in advance about their discontinuation.

Recommended transfer domains and resource records to DNS hosting (actual) now to avoid disruption of sites when DNS hosting (legacy) is down.

If you registered after January 30, you will only have access to the DNS hosting (actual).

A resource record is a record of matching domain and domain information in the Domain Name System (DNS).

In DNS hosting, you cannot manage reverse resource records (PTR records), to to do that, use IP address accounting service.

Add a resource record

In DNS hosting (actual), resource records are stored in groups — one group contains all the resource records of a domain with the same type. For example, when DNS balancing all IP addresses of the domain will be stored in one A-record group.

If you do not already have a resource record group of the correct type for the domain, add a resource record group of that type. If you already have a group of resource records of the desired type, add an additional value to it.

Add a group of resource records

  1. In control panel go to DNSDomain zones.

  2. Open the zone page.

  3. Click Add.

  4. Enter the name of the resource record group — this is the domain for which the group will be created. You can create a resource record group:

    • for the primary domain (zone name) — leave the field blank. For example, if you leave the field blank for the zone example.com.a group will be created with the name example.com.
    • for a subdomain — enter the first part of its name. For example, if you enter first for the area example.com.a group will be created with the name first.example.com.
  5. Select resource record type in the group — A, AAAA, TXT, CNAME, MX, NS, SRV, SSHFP, ALIAS, CAA, DNAME, HTTPS, SVCB.

  6. Enter TTL or leave the default value. TTL is the time in seconds for which a resource entry in the NS server cache is considered up to date and does not need to be re-cached. The TTL of a group applies to all resource records in the group.

  7. Enter the value of the resource record, for example, for an A record, the IP address to be mapped to the domain name.

  8. If you need to add another resource record to the group, click Add and enter the value of the record.

  9. Optional: enter a comment — any additional information about the group. The comment will be displayed only in DNS hosting.

  10. Click Add.

  11. Wait for the added resource record group to propagate to the DNS servers. Propagation can take up to 72 hours.

  12. Optional: check resource records. If 72 hours after creation the resource records have not appeared on the DNS servers, file a ticket.

Add a resource record to a group

If you add a resource record to an existing group, it will have the name and TTL that are specified for the group.

  1. In control panel go to DNSDomain zones.
  2. Open the zone page.
  3. On the menu. of resource record groups, select Edit.
  4. Click Add.
  5. Enter a value.
  6. Click Save.
  7. Wait for the resource record to propagate to the DNS servers. Propagation can take up to 72 hours from the TTL of the group. You can view the TTL of a resource record group in control panels under DNSDomain zones → zone page.
  8. Optional: check the resource record. If the resource record has not appeared on the DNS servers 72 hours after creation, file a ticket.

Available resource record types

Learn more about the purpose of the different resource records, their logic and limitations in this Selectel blog article How to figure out DNS hosting and not break anything.

AAssociates a domain name with the IP address of a server on an IPv4 network. Unless an A-record is created for the domain, the site will not work
AAAAAssociates a domain name with the IP address of a server on an IPv6 network. Unless an AAAA record is created for the domain, the site will not work
ALIASBinds an alias domain to the main (canonical) domain so that the subdomain leads to the IP address of the canonical domain. Similar in logic to a CNAME record, but can be added for second-level domains and can exist with other resource records for the domain (except A and AAAA)
CAAIndicates certificate authorities that are allowed to issue TLS(SSL) certificates for this domain name. If multiple CAs can issue certificates for the domain, a CAA record must be created for each CA
CNAMEBinds the additional domain to the primary (canonical) domain so that both lead to the IP address of the primary domain. A CNAME record cannot be added for a second-level domain. A domain with a CNAME record cannot have other resource records
DNAMEBinds all subdomains to the main (canonical) domain so that they lead to the IP address of the main domain.
MXIndicates the server to receive incoming mail for the domain. If the domain has multiple mail servers, an MX record must be created for each server, indicating the priority for load balancing
NSIndicates the DNS servers where the domain name resource records are stored. When you add a domain to DNS hosting (actual), NS records for the domain are created automatically and cannot be edited or deleted. You can only create NS records for a subdomain
SOAContains information about the domain zone, created automatically when the zone is created in DNS hosting (actual). SOA record cannot be edited or deleted
SRVSpecifies the location — hostname and port number of servers for specific services. For each SRV record, it also specifies the server priority and record weight for load balancing between servers
SSHFPContains the key fingerprint that is used by the server when connecting via SSH protocol
SVCBContains data for establishing a connection to the site: preferred protocol and its version, IP addresses and ports
HTTPSSpecialized analog of SVCB record for HTTPS connection establishment
TXTContains any textual information to be added to the domain settings. For example, it can store a unique token to validate domain rights or a DKIM key for outgoing mailings