Skip to content

docs: replace Contact Fern with self-serve custom domain setup instructions#6100

Open
fern-api[bot] wants to merge 1 commit into
mainfrom
devin/improve-custom-domain-docs
Open

docs: replace Contact Fern with self-serve custom domain setup instructions#6100
fern-api[bot] wants to merge 1 commit into
mainfrom
devin/improve-custom-domain-docs

Conversation

@fern-api

@fern-api fern-api Bot commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Summary

Replaces all "Contact Fern" steps in the custom domain setup documentation with self-serve instructions. Customers can now complete the entire custom domain setup without contacting support.

Changes

setting-up-your-domain.mdx (manual setup page):

  • Replaced "Contact Fern" steps with "Verify domain ownership" steps documenting the TXT records (_fern-verification and _vercel)
  • Updated CNAME target from a per-project value to the standard cname.vercel-dns.com
  • Added fern generate --docs after each docs.yml update step
  • Added Troubleshooting section: Vercel error page (DEPLOYMENT_NOT_FOUND) diagnosis and SSL certificate issues
  • Removed "contact Fern" from the Multiple custom domains section

domains.mdx (Dashboard page):

  • Added explicit "Verify domain ownership" step with TXT record details
  • Added specific DNS record values per domain type (CNAME, A record)
  • Added Troubleshooting section matching the manual page

Context

Surfaced by a customer who reported custom domain setup was "annoyingly complicated" — the DNS step previously just said "reach out to sales" with no actual instructions, and they hit a Vercel DEPLOYMENT_NOT_FOUND error because ownership verification wasn't documented.

@fern-api fern-api Bot requested a review from devalog as a code owner July 7, 2026 11:20

### Vercel error page after pointing DNS

A Vercel error page with an error ID like `cdg1::...` (often `DEPLOYMENT_NOT_FOUND`) means DNS is pointing to Vercel but domain ownership verification has not completed. Confirm both TXT records are in place, wait for propagation, and click **Verify Ownership** again.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🚫 [vale] reported by reviewdog 🐶
[Microsoft.Contractions] Use 'hasn't' instead of 'has not'.


A Vercel error page with an error ID like `cdg1::...` (often `DEPLOYMENT_NOT_FOUND`) means DNS is pointing to Vercel but domain ownership verification has not completed. Confirm both TXT records are in place, wait for propagation, and click **Verify Ownership** again.

### SSL certificate not provisioning

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

📝 [vale] reported by reviewdog 🐶
[FernStyles.Headings] 'SSL certificate not provisioning' should use sentence-style capitalization.


### Vercel error page after pointing DNS

A Vercel error page with an error ID like `cdg1::...` (often `DEPLOYMENT_NOT_FOUND`) means DNS is pointing to Vercel but domain ownership verification has not completed. To resolve:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🚫 [vale] reported by reviewdog 🐶
[Microsoft.Contractions] Use 'hasn't' instead of 'has not'.

2. Wait for DNS propagation (up to 10 minutes).
3. Return to the [Fern Dashboard](https://dashboard.buildwithfern.com/) and click **Verify Ownership** again.

### SSL certificate not provisioning

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

📝 [vale] reported by reviewdog 🐶
[FernStyles.Headings] 'SSL certificate not provisioning' should use sentence-style capitalization.

@github-actions

github-actions Bot commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant