Skip to content

Commit d6552c0

Browse files
authored
fix(dns): reformat Domains & DNS records page (#4989)
* fix(dns): reformat * fix(dns): fix record
1 parent 6ce7cfb commit d6552c0

File tree

1 file changed

+27
-43
lines changed

1 file changed

+27
-43
lines changed

pages/domains-and-dns/reference-content/understanding-dns-records.mdx

Lines changed: 27 additions & 43 deletions
Original file line numberDiff line numberDiff line change
@@ -20,31 +20,27 @@ Information in DNS zones is categorized and organized through a list of [DNS rec
2020
Each of these records has a type, an expiration time (Time to Live - TTL) and a name. Certain types of records also have type-specific data.
2121

2222

23-
### A record
23+
## A record
2424

2525
**A record** stands for **Address record**. It is mostly used to map domain names to the IPv4 address of a specific server. In other words, it allows to connect a domain name to the numerical IP address of a server where the website or online service is hosted.
2626

2727
An A record ensures that when you type a website's name into your browser, your computer knows where to find that website on the internet.
2828

29-
### AAAA record
29+
## AAAA record
3030

3131
Just like an A record connects a domain to an IPv4 address, an **AAAA record** does the same thing for the newer IPv6 addresses. It allows devices to locate and communicate with websites and services using the IPv6 protocol.
3232

33-
### ALIAS record
33+
## ALIAS record
3434

3535
An ALIAS record works exactly like a [CNAME record](#cname-record)
3636

3737
An ALIAS record could be useful if you want your domain name (not its subdomains) to point to a hostname.
3838

3939
<Message type="important">
40-
You must end your domain with a **trailing dot** as this disables domain search, using only the complete domain name you have given.<br />
41-
<br />
42-
Not ending your domain name with a trailing dot results in your domain being tried with a domain name appended to it, or even a list of domain names until one [resolves](/domains-and-dns/concepts/#domain-name-resolution).<br />
43-
<br />
44-
For example, if you want `mydomain.com` to point to `mynewdomain.com`, you **must** write `mynewdomain.com.` in the **Hostname** field. Otherwise, the CNAME record will direct your users to `mynewdomain.com.mynewdomain.com`.<br />
40+
Ensure you add a [trailing dot](#formatting-note-trailing-dot) when creating an ALIAS record.
4541
</Message>
4642

47-
### CAA record
43+
## CAA record
4844

4945
**CAA record** stands for **Certification Authority Authorization record**. It allows domain owners to specify which certificate authorities (CAs) are authorized to issue [SSL/TLS certificates](/domains-and-dns/concepts/#ssltls-certificates) for their domain.
5046

@@ -68,45 +64,33 @@ The CAA record provided with Domains and DNS includes the following components:
6864

6965
* **128 or Issuer critical**: This flag means that any unrecognized tags will halt the certificate issuance, assuming the issuer is compliant to standards.
7066

71-
### CNAME record
67+
## CNAME record
7268

7369
**CNAME record** stands for **Canonical name record**. It is used to point subdomains to a hostname. A CNAME record does not directly [resolve](/domains-and-dns/concepts/#domain-name-resolution) to an IP address. Instead, it refers to whether the domain is an [absolute](/domains-and-dns/concepts/#fully-qualified-domain-name-fqdn) or [relative](/domains-and-dns/concepts/#partially-qualified-domain-name-pqdn) domain.
7470

7571
<Message type="important">
76-
You must end your domain with a **trailing dot** as this disables domain search, using only the complete domain name you have given.<br />
77-
<br />
78-
Not ending your domain name with a trailing dot results in your domain being tried with a domain name appended to it, or even a list of domain names until one [resolves](/domains-and-dns/concepts/#domain-name-resolution).<br />
79-
<br />
80-
For example, if you want `mydomain.com` to point to `mynewdomain.com`, you **must** write `mynewdomain.com.` in the **Hostname** field. Otherwise, the CNAME record will direct your users to `mynewdomain.com.mynewdomain.com`.<br />
72+
Ensure you add a [trailing dot](#formatting-note-trailing-dot) when creating a CNAME record.
8173
</Message>
8274

83-
### DNAME record
75+
## DNAME record
8476

8577
**DNAME record** stands for **Delegation name record**. It is used for domain name redirection and renaming. Unlike other DNS record types that map domain names to IP addresses, a DNAME record allows you to redirect an entire domain and all of its subdomains to a different domain name.
8678

8779
You should configure a DNAME record if you want to rename or restructure a domain while ensuring that all of its subdomains are automatically redirected to the new domain.
8880

8981
<Message type="important">
90-
You must end your domain with a **trailing dot** as this disables domain search, using only the complete domain name you have given.<br />
91-
<br />
92-
Not ending your domain name with a trailing dot results in your domain being tried with a domain name appended to it, or even a list of domain names until one [resolves](/domains-and-dns/concepts/#domain-name-resolution).<br />
93-
<br />
94-
For example, if you want `mydomain.com` to point to `mynewdomain.com`, you **must** write `mynewdomain.com.` in the **Hostname** field. Otherwise, the CNAME record will direct your users to `mynewdomain.com.mynewdomain.com`.<br />
82+
Ensure you add a [trailing dot](#formatting-note-trailing-dot) when creating a DNAME record.
9583
</Message>
9684

97-
### MX record
85+
## MX record
9886

9987
**MX record** stands for **Mail exchange record**. It is used to specify the mail servers responsible for receiving and handling emails for a specific domain. For example, when sending an email to an address within your domain `[email protected]`, your email server needs to determine where to deliver the emails. Your MX record provides this information by pointing to the receiver domain's mail servers that are designated to accept incoming emails.
10088

10189
<Message type="important">
102-
You must end your domain with a **trailing dot** as this disables domain search, using only the complete domain name you have given.<br />
103-
<br />
104-
Not ending your domain name with a trailing dot results in your domain being tried with a domain name appended to it, or even a list of domain names until one [resolves](/domains-and-dns/concepts/#domain-name-resolution).<br />
105-
<br />
106-
For example, if you want `mydomain.com` to point to `mynewdomain.com`, you **must** write `mynewdomain.com.` in the **Hostname** field. Otherwise, the CNAME record will direct your users to `mynewdomain.com.mynewdomain.com`.<br />
90+
Ensure you add a [trailing dot](#formatting-note-trailing-dot) when creating an MX record.
10791
</Message>
10892

109-
### NAPTR record
93+
## NAPTR record
11094

11195
**NAPTR record** stands for **Naming Authority Pointer record**. It provides instructions for translating a specific type of data into a different format. NAPTR records help devices and services such as Voice over Internet Protocol systems, find the appropriate servers or services to connect to. They essentially act as a guide, pointing out how to transform certain data to match what is needed for communication or service interaction.
11296

@@ -136,45 +120,45 @@ The NAPTR record provided with Domains and DNS includes the following components
136120

137121
- **Replacement domain**: A replacement string that is used to replace the matched portion of the domain name based on the regular expression.
138122

139-
### NS record
123+
## NS record
140124

141125
**NS record** stands for **Name server record**. It is used to designate the authoritative name servers for a specific domain.
142126

143127
When a DNS query is made for a domain's information (like its IP address), DNS resolvers will follow the NS records to determine which authoritative name servers to contact for that domain.
144128
The authoritative name servers then provide the necessary DNS information to complete the query.
145129

146130
<Message type="important">
147-
You must end your domain with a **trailing dot** as this disables domain search, using only the complete domain name you have given.<br />
148-
<br />
149-
Not ending your domain name with a trailing dot results in your domain being tried with a domain name appended to it, or even a list of domain names until one [resolves](/domains-and-dns/concepts/#domain-name-resolution).<br />
150-
<br />
151-
For example, if you want `mydomain.com` to point to `mynewdomain.com`, you **must** write `mynewdomain.com.` in the **Hostname** field. Otherwise, the CNAME record will direct your users to `mynewdomain.com.mynewdomain.com`.<br />
131+
Ensure you add a [trailing dot](#formatting-note-trailing-dot) when creating a NS record.
152132
</Message>
153133

154-
### SRV record
134+
## SRV record
155135

156136
**SRV record** stands for **Service record**. It provides information about specific network services offered by a domain.
157137

158138
It includes details like the service's protocol, port number, priority, weight, and the domain name of the server offering the service. SRV records help devices locate and connect to the right servers for specific services on the internet such as chat or phone services.
159139

160140
<Message type="important">
161-
You must end your domain with a **trailing dot** as this disables domain search, using only the complete domain name you have given.<br />
162-
<br />
163-
Not ending your domain name with a trailing dot results in your domain being tried with a domain name appended to it, or even a list of domain names until one [resolves](/domains-and-dns/concepts/#domain-name-resolution).<br />
164-
<br />
165-
For example, if you want `mydomain.com` to point to `mynewdomain.com`, you **must** write `mynewdomain.com.` in the **Hostname** field. Otherwise, the CNAME record will direct your users to `mynewdomain.com.mynewdomain.com`.<br />
141+
Ensure you add a [trailing dot](#formatting-note-trailing-dot) when creating a SRV record.
166142
</Message>
167143

168-
### TLSA record
144+
## TLSA record
169145

170146
**TLSA record** stands for **Transport Layer Security Authentication record**. It is used to associate a TLS certificate or public key with the specified domain name.
171147

172148
TLSA records allow you to improve the security of encrypted connections by specifying how clients should verify the authenticity of the server's certificate when establishing a TLS connection.
173149

174150
When a client connects to a server using TLS and encounters a TLSA record, it can use the information in the record to verify that the presented certificate matches the expected one. This adds an extra layer of security by making sure that encrypted connections are established with legitimate servers.
175151

176-
### TXT record
152+
## TXT record
177153

178154
**TXT record** stand for **Text record**. It consists of plain text data, and its content can be human-readable or machine-interpretable, depending on its intended purpose.
179155

180-
TXT records can be used for various purposes such as adding information, verification, authentication, and configuration settings to a domain.
156+
TXT records can be used for various purposes such as adding information, verification, authentication, and configuration settings to a domain.
157+
158+
## Formatting note: trailing dot
159+
160+
In the case of ALIAS, CNAME, DNAME, MX, NS and SRV records, you **must** end your domain with a **trailing dot** to use only the complete hostname you have given.
161+
162+
Not ending your domain name with a trailing dot can result in your domain being tried with a domain name appended to it, or even a list of domain names until one [resolves](/domains-and-dns/concepts/#domain-name-resolution).
163+
164+
For example, if you create a CNAME record to point `mydomain.com` to `mynewdomain.com`, you must write `mynewdomain.com.` (with a trailing dot) in the Hostname field. Otherwise, the DNS resolver may try to resolve `mynewdomain.com.mydomain.com`, leading to incorrect behavior.

0 commit comments

Comments
 (0)