DOC-1046: Add Cloudflare to Gcore DNS migration guide#2102
Open
JojoVilloso wants to merge 1 commit into
Open
Conversation
Adds a new how-to doc covering the full migration process from Cloudflare DNS to Gcore Managed DNS, including TTL prep, zone file export/import, registrar-level nameserver update, and propagation verification. Refs: DOC-1046 Co-authored-by: Cursor <cursoragent@cursor.com>
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
1 participant
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
Adds a new how-to guide covering the full DNS migration process from Cloudflare to Gcore Managed DNS.
Covers:
Key callout: Includes a prominent warning that NS changes must be made at the registrar level — not inside Cloudflare — based on real support case from the original ticket thread.
Pending: Legal review required for third-party (Cloudflare) mentions per DOC-1233 policy.
Closes DOC-1046
Made with Cursor