Skip to content

Commit 1be8e11

Browse files
Add section for email records with examples
1 parent cc6032d commit 1be8e11

File tree

1 file changed

+39
-2
lines changed

1 file changed

+39
-2
lines changed

src/content/docs/dns/manage-dns-records/how-to/initial-setup.mdx

Lines changed: 39 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ sidebar:
55
order: 1
66
---
77

8-
import { GlossaryTooltip, GlossaryDefinition, Render, TabItem, Tabs, Details, Example, } from "~/components";
8+
import { GlossaryTooltip, GlossaryDefinition, Render, TabItem, Tabs, Details, Example } from "~/components";
99

1010
As explained in the [overview page](/dns/manage-dns-records/), DNS records are essential, as they are used to make your website or application available to visitors and other web services.
1111

@@ -75,4 +75,41 @@ If you are using other providers, look for their guidance on how to connect doma
7575

7676
Most subdomains serve a specific purpose within the overall context of your website. For example, `blog.example.com` might be your blog, `support.example.com` could be your customer help portal, and `store.example.com` would be your e-commerce site.
7777

78-
Even if you do not require specific subdomains, you might want to set up at least the `www` subdomain. It will usually point to the same content as what you have on the apex domain (`example.com`) or use a [redirect](/fundamentals/setup/manage-domains/manage-subdomains/#redirect-a-subdomain-to-the-apex-domain). Having a DNS record on the `www` subdomain helps guarantee that a visitor who types `www.` in front of your domain address on their browser can still find your website or application.
78+
Even if you do not require specific subdomains, you might want to set up at least the `www` subdomain. It will usually point to the same content as what you have on the apex domain (`example.com`) or use a [redirect](/fundamentals/setup/manage-domains/manage-subdomains/#redirect-a-subdomain-to-the-apex-domain). Having a DNS record on the `www` subdomain helps guarantee that a visitor who types `www.` in front of your domain address on their browser can still find your website or application.
79+
80+
## Email records
81+
82+
Depending on your business needs, you can configure DNS records so that you can:
83+
84+
- use your domain to receive emails
85+
- receive and send emails from your domain
86+
- prevent others from sending emails on your behalf (spoofing)
87+
88+
When you send and receive emails, you can expect to find mail exchange (MX) records and address records (A or AAAA) pointing to IP addresses specified by your SMTP provider.
89+
90+
<Details header="Example">
91+
<Example>
92+
DNS management for **example.com**:
93+
94+
| Type | Name | Content | Proxy status | TTL |
95+
| ---- | ------- | ------------ | ------------ | ------ |
96+
| A | `mail` | `192.0.2.1` | DNS Only | Auto |
97+
| MX | `example.com` | `john.mx.example-server.test [1]` | DNS Only | Auto |
98+
99+
</Example>
100+
</ Details>
101+
102+
For security records that prevent domain spoofing, you can expect to find TXT records for Sender Policy Framework [(SPF)](https://www.cloudflare.com/learning/dns/dns-records/dns-spf-record/), DomainKeys Identified Mail [(DKIM)](https://www.cloudflare.com/learning/dns/dns-records/dns-dkim-record/), and Domain-based Message Authentication Reporting and Conformance [(DMARC)](https://www.cloudflare.com/learning/dns/dns-records/dns-dmarc-record/).
103+
104+
<Details header="Example">
105+
<Example>
106+
DNS management for **example.com**:
107+
108+
| Type | Name | Content | Proxy status | TTL |
109+
| ---- | ------- | ------------ | ------------ | ------ |
110+
| TXT | `_dmarc` | `"v=DMARC1; p=reject; sp=...` | DNS Only | Auto |
111+
| TXT | `*._domainkey` | `"v=DKIM1; p="` | DNS Only | Auto |
112+
| TXT | `example.com` | `"v=spf1 -all"` | DNS Only | Auto |
113+
114+
</Example>
115+
</ Details>

0 commit comments

Comments
 (0)