Skip to content

[Domain Connect] add instructions about the most common problem point#28269

Merged
RebeccaTamachiro merged 3 commits intocloudflare:productionfrom
kerolasa:domain-connect-pubkey
Feb 12, 2026
Merged

[Domain Connect] add instructions about the most common problem point#28269
RebeccaTamachiro merged 3 commits intocloudflare:productionfrom
kerolasa:domain-connect-pubkey

Conversation

@kerolasa
Copy link
Contributor

This adds new bullet 2. to segment 'Contact Cloudflare to onboard your template' asking template onboarding to include public key TXT record in submission. The pubkey record has turned out to be most common issue causing perhaps half of the back & forth with Cloudflare and external service providers. Hope is that with early check, and additional validation hints these issues become quicker and easier to deal with.

The page: https://developers.cloudflare.com/dns/reference/domain-connect/

@kerolasa kerolasa requested review from a team and RebeccaTamachiro as code owners February 11, 2026 16:31
@github-actions github-actions bot added product:dns Issues or PRs related to DNS size/s labels Feb 11, 2026
1. List of template(s) you want to onboard, with their corresponding GitHub hyperlinks.
2. A logo to be displayed as part of the Domain Connect flow. Preferably in `SVG` format.
3. The default [proxy status](/dns/proxy-status/) you would like Cloudflare to set for `A`, `AAAA`, and `CNAME` records that are part of your template(s). Proxying other record types is not supported.
2. Fully qualified host name(s) of the syncPubKeyDomain TXT record(s).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/bonk this should be a link to /dns/reference/domain-connect/ + reference the Domain Connect spec and use backticks since it's a property name.

review this doc and fix any clarity or style guide issues.

This adds new bullet 2. to segment 'Contact Cloudflare to onboard your
template' asking template onboarding to include public key TXT record
in submission.  The pubkey record has turned out to be most common issue
causing perhaps half of the back & forth with Cloudflare and external
service providers.  Hope is that with early check, and additional
validation hints these issues become quicker and easier to deal with.

Review: cloudflare#28269
Signed-off-by: Sami Kerola <kerolasa@cloudflare.com>
Include date and time in troubleshooting emails.  This hopefully helps with
help requests that inform something failed, but causes Cloudflare to have
problem finding the issue from logs.  And in same go, be a little bit more
precise with terminology.

Signed-off-by: Sami Kerola <kerolasa@cloudflare.com>
@kerolasa
Copy link
Contributor Author

kerolasa commented Feb 12, 2026

I just updated this pull request. In this update there are

  • backticks to syncPubKeyDomain
  • host name became fqdn, as per feedback from Rebecca in the company chat
  • new commit: troubleshooting includes date & time of issue, and generally clarifies the troubleshooting information request

@kerolasa kerolasa force-pushed the domain-connect-pubkey branch from 730f43e to c57a084 Compare February 12, 2026 09:50
@RebeccaTamachiro RebeccaTamachiro enabled auto-merge (squash) February 12, 2026 16:17
@RebeccaTamachiro RebeccaTamachiro merged commit e13d3c5 into cloudflare:production Feb 12, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

product:dns Issues or PRs related to DNS size/s

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants