Add missing name server content: migration guide, redundancy article, and cleanup#1817
Open
stephanoodle wants to merge 4 commits intomainfrom
Open
Add missing name server content: migration guide, redundancy article, and cleanup#1817stephanoodle wants to merge 4 commits intomainfrom
stephanoodle wants to merge 4 commits intomainfrom
Conversation
…de, retire old troubleshooting article
47dc9f8 to
9c0d352
Compare
The name_servers.yaml restructure belongs in PR #1743 (pillar and category structure). This PR focuses on article content only.
Contributor
Author
Merge orderThis PR must merge after #1746, which creates Also note: both this PR and #1744 modify |
This was referenced Mar 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
migrating-dns-to-dnsimple.md) — How-to guide covering the full DNS migration process: record import, verification, name server switch, and propagation monitoring.name-server-redundancy.md) — Explanation article covering why multiple name servers matter, Anycast routing, and DNSimple's redundancy architecture.pointing-domain-to-dnsimple.md) — Rewritten from a thin routing page into a proper article with delegation context, name server list, propagation expectations, and troubleshooting links.troubleshoot-dnsimple-name-servers.md) — Deleted and redirected to/articles/troubleshooting-name-servers/. Updated all internal cross-links (4 articles) to point to the new URL.categories/name_servers.yamlwith the two new articles.Dependencies
This PR should be merged after PR #1746, which creates the redirect target (
troubleshooting-name-servers.md).Test plan
/articles/troubleshoot-dnsimple-name-servers/resolves to/articles/troubleshooting-name-servers/dns.md,check-resolution-status.md,resolution-status.md, anddomain-resolution-issues.mdpoint to valid targets