Skip to content

[Email Security] Add TTL note #22465

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 15, 2025
Merged

[Email Security] Add TTL note #22465

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4d05143
[Email Security] Add TTL note
Maddy-Cloudflare May 15, 2025
d269f52
Update src/content/partials/cloudflare-one/email-security/deployment/…
Maddy-Cloudflare May 15, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions ...rtials/cloudflare-one/email-security/deployment/mx-deployment-prerequisites.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,10 @@ To ensure changes made in this tutorial take effect quickly, update the Time to

Changing the TTL value instructs DNS servers on how long to cache this value before requesting an update from the responsible nameserver. You need to change the TTL value before changing your MX records to Email Security. This will ensure that changes take effect quickly and can also be reverted quickly if needed. If your DNS manager does not allow for a TTL of five minutes, set it to the lowest possible setting.

:::note
Make TTL changes a few days before the production update, and wait at least as long as the old TTL values before making the update, since some senders might still be using the old cached values.
:::

To check your existing TTL, open a terminal window and run the following command against your domain:

```sh
Expand Down
Loading