[bigbadbillperry]

Title: docs(dns): Clarify GoDaddy DS record tab availability after nameserver changes

Description:

Summary

Add a GoDaddy-specific troubleshooting note to the DNSSEC setup documentation.

Problem

After changing a domain's authoritative nameservers from GoDaddy to Cloudflare, GoDaddy's domain management interface may continue displaying the DNSSEC activation tab instead of the DS Records tab.

Attempting to enable DNSSEC through the original interface can produce an error.

Resolution

Refreshing GoDaddy's domain management page after the nameserver change causes the appropriate DS Records tab to appear.

Testing

Verified during an actual domain migration on October 30, 2026. The DS record was successfully entered using GoDaddy's DS Records interface.

This is a documentation-only change. No application code or DNS functionality is modified.

[cloudflare-docs-bot]

AI Review

✅ Reviewed a1a019f · 3 findings · incremental

👉 Fix in your agent 👈

Fix the following review findings in PR #34811 (https://github.com/cloudflare/cloudflare-docs/pull/34811).

Before making changes, review each finding and present a brief summary table:
- For each finding, state whether you agree, disagree, or need clarification.
- If you disagree, explain why.
- If you need clarification before deciding, ask those questions.
- Then share your plan for which issues to tackle and in what order.

After triaging, follow this order:
1. Post a comment on this PR for any findings you are skipping, with the finding ID and your reasoning.
2. Then commit the fixes for the legitimate findings.

The comment must come before the commit because the next review reads PR comments.

## Style Guide
- S-0153e8fd | src/content/docs/dns/dnssec/index.mdx:50 | Use `go to` instead of `navigate to`
  Prose uses `navigate to` in a UI instruction; per the writing style rules it should be `go to`.
- S-10f098f3 | src/content/docs/dns/dnssec/index.mdx:55 | Time-sensitive content: month name and year
  Prose outside `src/content/changelog/` contains a month name (`October`) and a four-digit year (`2026`) in the sentence "...observed during a GoDaddy-to-Cloudflare DNS migration in October 2026." Time-sensitive references must be removed or rewritten so docs read as timeless.

## Conventions
- V-1b594e76 | PR | PR title does not identify the affected product or content area
  The PR title is `Update index.mdx`, which does not identify the affected product, feature, or content area. This is a docs-content change to the DNSSEC setup documentation (`src/content/docs/dns/dnssec/index.mdx`); a title like the one embedded in the body (identifying DNS/DNSSEC and the GoDaddy DS record guidance) would satisfy the convention.

Style Guide

• src/content/docs/dns/dnssec/index.mdx:50 · Use go to instead of navigate to

  Prose uses navigate to in a UI instruction; per the writing style rules it should be go to.

• src/content/docs/dns/dnssec/index.mdx:55 · Time-sensitive content: month name and year

  Prose outside src/content/changelog/ contains a month name (October) and a four-digit year (2026) in the sentence "...observed during a GoDaddy-to-Cloudflare DNS migration in October 2026." Time-sensitive references must be removed or rewritten so docs read as timeless.

Conventions

• PR · PR title does not identify the affected product or content area

  The PR title is Update index.mdx, which does not identify the affected product, feature, or content area. This is a docs-content change to the DNSSEC setup documentation (src/content/docs/dns/dnssec/index.mdx); a title like the one embedded in the body (identifying DNS/DNSSEC and the GoDaddy DS record guidance) would satisfy the convention.

Commands

• /review Run a review now.
• /full-review Review the entire PR diff.
• /disable-auto-review Stop automatic reviews.
• /rebase Rebase against production.

[cloudflare-docs-bot]

Review coverage

🟡 1 ownership area needs approval.

Suggested reviewers: @chreo @hannes-cf

Needs approval	Eligible approvers	Suggested
dns	@chreo, @dklbreitling, @esomoza-cf, @fattouche, @hannes-cf, @kerolasa, @matildeopbravo, @mworsley-cloudflare, @sebastiaanyn, @svenr-cf, @vavrusa, @vendemiat, @Woutifier, @xofyarg, @cloudflare/product-owners	chreo, hannes-cf

CODEOWNERS mappings for displayed areas (1)

Pattern	Owners
/src/content/docs/dns/	@chreo, @dklbreitling, @esomoza-cf, @fattouche, @hannes-cf, @kerolasa, @matildeopbravo, @mworsley-cloudflare, @sebastiaanyn, @svenr-cf, @vavrusa, @vendemiat, @Woutifier, @xofyarg, @cloudflare/product-owners

[bigbadbillperry]

A little additional context on how I discovered this:

I spent an embarrassingly long time banging my head against the wall trying to figure this out. I even consulted a couple of AI assistants, both of which confidently assured me that the "DS Records" tab should be there. It wasn't.

I navigated through several sections of GoDaddy's domain management interface, repeatedly returning to Domain → DNS, but the interface continued displaying the original "DNSSEC" tab. Attempting to enable DNSSEC there resulted in an error.

Eventually, I refreshed the browser page, and suddenly the DS Records tab appeared exactly where it was supposed to be.

Simply navigating away and returning wasn't sufficient. A full page refresh was required.

I'm sharing this because it's a small but frustrating UI behavior that could easily waste another user's time. A one-sentence troubleshooting note in the documentation would have saved me quite a bit of it.

Hopefully, this contribution saves someone else the same experience!