Skip to content
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

typo fix in dns-propagation.md #9287

Merged
merged 2 commits into from
Oct 30, 2024
Merged

typo fix in dns-propagation.md #9287

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8caf0f7
typo fix in dns-propagation.md
stevector Oct 30, 2024
4813846
typo fix
stevector Oct 30, 2024
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
2 changes: 1 addition & 1 deletion source/content/partials/dns-prep.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ reviewed: ""

Follow these simple steps to help minimize DNS-related downtime when you're planning a site migration:

1. Lower the TTL values as low as allowed (usually `500`) several days in advance at your DNS service manager. That way when the values are changed, new records are propagated faster.
1. Lower the TTL values as low as allowed (usually `300`) several days in advance at your DNS service manager. That way when the values are changed, new records are propagated faster.

1. Use `dig` to confirm the new TTL values have propagated to your ISP's DNS servers:

Expand Down
2 changes: 1 addition & 1 deletion source/content/partials/dns-propagation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,6 @@ tags: [--]
reviewed: ""
---

Every DNS record has a **Time To Live** (**TTL**) value, which specifies how long any DNS server should hold that record, before dropping it and asking for a new version from its upstream DNS provider. TTLs are usually set in seconds with a few common ones being `86400` (24 hours), `43200` (12 hours), `3600` (1 hour), and `500` (5 minutes).
Every DNS record has a **Time To Live** (**TTL**) value, which specifies how long any DNS server should hold that record, before dropping it and asking for a new version from its upstream DNS provider. TTLs are usually set in seconds with a few common ones being `86400` (24 hours), `43200` (12 hours), `3600` (1 hour), and `300` (5 minutes).

**DNS Propagation** is the time it takes for changes made to DNS records to be reflected across DNS servers globally. A lower TTL value means faster propagation, but it's important to note that it is not a 1:1 ratio. Between your [authoritative name server](#where-are-my-dns-records-hosted) and the DNS servers of any particular ISP could be any number of intermediate DNS servers. Each server in that chain will wait for the records it holds to expire before requesting new ones. Because of this, it can take *several times longer* than your record's TTL value to see changes reflected for everyone.
Loading