DS records that are vital for the proper configuration of the DNS servers listed on the online management platform should be managed directly on the platform, in accordance with the DS registrations that are supported. The details for each registration type may be consulted in the technical reference documents drafted by the Internet Engineering Task Force (IETF).

Type of record Purpose Reference document
A Associate a domain name with an IPv4 address so that the server is able to communicate. RFC 1035
AAAA Associate a domain name with an IPv6 address so that the server is able to communicate. RFC 3596
CAA (Certification Authority Restriction) Specify the certification authority(ies) (CA) authorised to issue certificates for a particular domain name. RFC 6844
CNAME Redirect one request towards another, in particular in order to bring in traffic from several different domains to a single location. Notes :
  • A CNAME can only be applied to names registered under a particular domain,
  • Where a CNAME is defined for a particular name, no other DNS record type can be defined for the same name.
 RFC 1035
DNSKEY (DNS Public Key) Sign and authenticate the DNS's Resource Record Sets (RRsets) using the public keys used in the DNSSEC authentication process.
DS (Delegation Signer) Check the DNSSEC key for a particular sub-domain.
MX (mail exchange) Define the incoming mail servers for email. RFC 1035
NAPTR (Naming Authority Pointer) Rewrite a domain name based on common expressions, which could then be used as a URL, search for additional domain names, etc.
NS (authoritative name server) Spécifier l’hôte faisant autorité pour une zone et un domaine spécifié (serveurs de nom, délégation). RFC 1035
SOA (start of authority) Mark the start of authority for a particular DNS zone. Note: The DNS zone for a particular domain name is automatically pre- populated with a SOA that cannot be changed by the user. RFC 1035
SPF (Sender Policy Framework) Specify the hosts authorised to use the names and the ADministrative Management Domain (ADMD) mail recipients. RFC 7208
SRV (Server Selection) Associate several servers to a single domain, move services from one host to another without too much difficulty and nominate certain hosts as primary servers for a particular service and others as backup servers. RFC 2782
SSHFP (Secure Shell Key Fingerprints) Provide secure, remote login and other secure network services over a non-secure network owing not only to server authentication of a client, but also to user authentication to the server. The fingerprint of the server's public key in the DNS by using DNSSEC is particularly sought. RFC 4255
TLSA (Transport Layer Security (TLS) Protocol) Specify the keys used on the TLS servers, in other words, encrypted communications by means of the TLS (Transport Layer Security) protocol RFC 6698
TXT  This arbitrary human-read text field is used to:
  • integrate the information requested by instances to check that you are in fact the holder of the domain (Google, Adobe, etc.);
  • limit the servers able to send emails as part of its use via the SPF protocol.
 RFC 1035