As of Q2 2024, Gcore Managed DNS supports eleven record types. In this article, we provide introductory information about each of them.
Supported DNS record types
You can check the resource records of your domain name using the Gcore DNS Lookup tool.

​
A record

An А record defines the IP address to which the domain corresponds. The value of the A record is the server IP address in IPv4 format associated with your domain name. Here’s an example of an A record response: 
sample-test.com. 1800 IN A 1.2.3.4
Let’s break down what the components of an A record mean:
  • sample-test.com. is the domain name that corresponds to the server.
  • 1800 is the Time to Live (TTL) for the DNS record in seconds, which indicates how long the record is cached by servers or resolvers.
  • IN is the class that stands for “internet.”
  • A is the record type.
  • 1.2.3.4 is the IPv4 address of the server to which the domain name corresponds.
Example of adding an A record

​
AAAA record

An AAAA record defines the IP address to which the domain corresponds. The value of the AAAA record is the server IP address in IPv6 format that is associated with your domain name. Here’s an example of an AAAA record response: 
sample-test.com. 16015 IN AAAA 2606:2800:220:1:248:1893:25c8:1946
In this record, here is what each component means:
  • sample-test.com. is the domain name that corresponds to the server.
  • 16015 is the DNS record’s Time to Live (TTL) in seconds, which indicates how long the record is cached by servers or resolvers.
  • IN is the class that stands for “internet.”
  • AAAA is the record type.
  • 2606:2800:220:1:248:1893:25c8:1946 is the IPv6 address of the server to which the domain name corresponds.
Example of adding an AAAA record

​
NS record

An NS record defines the name of the authoritative name servers (primary and secondary are mandatory) to which you delegate your domain zone (where your zone is hosted). Gcore Managed DNS provides the following name servers for your domains: ns1.gcorelabs.net and ns2.gcdn.services. Example of NS records response: 
sample-test.com. 1869 IN NS a.iana-servers.net
sample-test.com. 1869 IN NS b.iana-servers.net
In these examples:
  • sample-test.com. is the domain name that delegates to the name servers.
  • 1869 is the Time to Live (TTL) for the DNS record in seconds, which indicates how long the record is cached by servers or resolvers.
  • IN is the class that stands for “internet.”
  • NS is the record type.
  • a.iana-servers.net and b.iana-servers.net are the authoritative name servers that contain information about the domain zone, and all added DNS records.
Example of adding an NS record

​
CNAME record

A CNAME (canonical name) record redirects from the domain name it’s associated with to another domain name. They effectively create an alias, allowing one domain name to repeat the configuration of another. When the resolver receives CNAME as an answer, it makes another request, or potentially a chain of requests. Make sure your configuration does not result in a loop. Here’s an example of a CNAME record response: 
www.sample-test.com. 3600 IN CNAME sample-test.com.
For CNAME, here’s what each part of the record means:
  • www.sample-test.com. is the domain name that inherits all records from another domain.
  • 3600 is the Time to Live (TTL) for the DNS record in seconds, which indicates how long the record is cached by servers or resolvers.
  • IN is the class that stands for “internet.”
  • CNAME is the record type.
  • sample-test.com. is the target domain name whose records are inherited by the domain www.sample-test.com.
Example of adding an CNAME record

​
MX record

An MX record defines the server that receives mail for the domain. Here’s an example of an MX record response: 
sample-test.com. 3600 IN MX 10 mail.sample-test.com.
In the case of an MX record, here’s what each part means:
  • sample-test.com. is the domain name for which the MX record is created.
  • 3600 is the Time to Live (TTL) for the DNS record in seconds, which indicates how long the record is cached by servers or resolvers.
  • IN is the class that stands for “internet.”
  • MX is the record type.
  • 10 is the priority of the mail server. If several servers are assigned for the domain, the server with the lowest priority will be the first to be contacted for mail delivery.
  • mail.sample-test.com. is the target host or the mail server which handles mail for sample-test.com.
Example of adding an MX record

​
TXT record

A TXT record provides additional textual information about the domain. For example, you can use a TXT record to specify Sender Policy Framework (SPF) rules determining which mail servers are authorized to send emails to your domain. Here’s an example of a TXT record response: 
sample-test.com. 15155 IN TXT "v=spf1 -all"
In this case:
  • sample-test.com. is the domain for which the SPF rules are set
  • 15155 is the Time to Live (TTL) for the DNS record in seconds, which indicates how long the record is cached by servers or resolvers.
  • IN is the class that stands for “internet.”
  • TXT is the record type.
  • "v=spf1 -all" is the actual SPF rule. v=spf1 indicates the SPF version being used, and -all means that no IP addresses are authorized to send an email for the domain. Any email that claims to be from this domain should be considered spoofed and can be safely rejected or marked as spam.
Example of adding a TXT record

​
SRV record

An SRV record identifies the server that provides specific services for the domain. For example, it can indicate the server providing internet telephony service (ITSP) for your domain. Example of an SRV record response: 
_sip._tcp.sample-test.com. 3600 IN SRV 10 50 5060 sipserver.sample-test.com.
For SRV records:
  • _sip._tcp.sample-test.com. is the name of the service and protocol used, as well as the domain that provides the service.
  • 3600 is the Time to Live (TTL) for the DNS record in seconds, which indicates how long the record is cached by servers or resolvers.
  • IN is the class that stands for “internet.”
  • SRV is the record type.
  • 10 is the priority, with a smaller number having a higher priority.
  • 50 is the weight used at equal priority for load balancing.
  • 5060 is the port on which the service is provided.
  • sipserver.sample-test.com. is the target host or server providing the service.
Example of adding a SRV record

​
CAA record

A CAA record specifies the certificate authorities (CAs) that are permitted to issue SSL/TLS certificates for the domain. Here’s an example of a CAA record response: 
sample-test.com. IN CAA 0 issue "letsencrypt.org"
In this instance:
  • sample-test.com. is the domain for which the CAA record is set.
  • IN is the class that stands for “internet.”
  • CAA is the record type.
  • 0 is the flag value which can indicate specific policy restrictions for the record.
  • issue is a tag that means that certificates can be issued by the specified certificate authority.
  • "letsencrypt.org" is a value that points to a specific Certificate Authority. In this case, Let’s Encrypt is the issuing CA for “example.com”, and only this CA can issue the certificates for the domain.
Example of adding a CAA record

​
HTTPS record

An HTTPS record provides information and connection parameters for accessing a web service via HTTPS. Here’s an example of an HTTPS record response: 
sample-test.com. 1800 IN HTTPS 1 . alpn=h3,h3-29,h2 ipv4hint=1.2.3.4,9.8.7.6 ipv6hint=2001:db8:3333:4444:5555:6666:7777:8888,2001:db8:3333:4444:CCCC:DDDD:EEEE:FFFF
In this instance:
  • sample-test.com. is the domain for which the HTTPS record is defined.
  • 1800 is the Time to Live (TTL) for the DNS record in seconds, which indicates how long the record is cached by servers or resolvers.
  • IN is the class that stands for “internet.”
  • HTTPS is the record type.
  • 1 is the priority, i.e., the number in the queue.
  • . stands for the host if it is the same as the domain name.
  • alpn=h3,h3-29,h2 specifies the application protocol versions.
  • ipv4hint=1.2.3.4,9.8.7.6 specifies IPv4 addresses.
  • ipv6hint=2001:db8:3333:4444:5555:6666:7777:8888,2001:db8:3333:4444:CCCC:DDDD:EEEE:FFFF specifies IPv6 addresses.
Example of adding an HTTPS record

​
SVCB record

An SVCB record specifies the transport protocols supported by the service and any associated optional parameters. This includes, for example, HTTP/2 and HTTP/3 over QUIC, but the specification is general and not limited to HTTP. Here’s an example of an SVCB record response: 
sample-test.com. 7200 IN SVCB 1 . alpn=h3
In an SVCB record:
  • sample-test.com. is the domain for which the SVCB record is set.
  • 7200 is the Time to Live (TTL) for the DNS record in seconds, which indicates how long the record is cached by servers or resolvers.
  • IN is the class that stands for “internet.”
  • SVCB is the record type.
  • 1 is the record priority. The lower the number, the higher the priority. The value 0 is reserved for alias mode, and 1 or higher is for service mode.
  • . is the TargetName. It’s the domain name of the server providing the service. In this case, the ”.” means the service is offered from the same domain as the one making the request, i.e., example.com.
  • alpn=h3 is a key-value pair from the SvcParamList. Here, alpn stands for “Application-Layer Protocol Negotiation” and h3 indicates support for HTTP/3.
Example of adding an SVCB record

​
PTR record

A PTR record maps an IP address to a domain or hostname. PTR records are primarily used for reverse DNS lookups and are necessary for certain applications, like some mail servers, that require sender domain verification.
InfoYou can add a PTR record only if your zone is under the top-level domain (TLD) in-addr.arpa (for IPv4) or ip6.arpa (for IPv6). After creating a zone under these TLDs, you can create a PTR record in the UI.
Here’s an example of a PTR record response: 
123.0.0.67.in-addr.arpa. 3600 IN PTR sample-test.com.
In this case:
  • 123.0.0.67.in-addr.arpa. is the reverse DNS format of the IP address. It’s written in the reverse order of the actual IP address, followed by in-addr.arpa for IPv4 addresses.
  • 3600 is the Time to Live (TTL) for the DNS record in seconds, which indicates how long the record is cached by servers or resolvers.
  • IN is the class that stands for “internet.”
  • PTR is the record type.
  • sample-test.com. is the hostname or domain to which the IP address resolves.

​
What’s next?

Add records using our guide on managing DNS records.