Skip to content

Update apex domain section for ngrok support #1634

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 20, 2025
Merged

Update apex domain section for ngrok support #1634

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
79bc333
Update apex domain section for ngrok support
samwho Oct 14, 2025
b39cc48
Merge branch 'main' into samwho-patch-1
samwho Oct 20, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 1 addition & 4 deletions universal-gateway/custom-domains.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,10 +49,7 @@ If you bring your own [wildcard domain](/universal-gateway/domains#wildcard-doma

## Apex domains

Because it's not possible to create `CNAME` records for apex domains (such as `example.com`), if you want to use an apex domain, you must use a DNS provider that supports an `ALIAS` record or `CNAME` flattening.

Due to how `ALIAS`/`CNAME` flattening is implemented, apex domains cannot take advantage of the [Global Load Balancer](/universal-gateway/global-load-balancer/).
If you're trying to create your apex domain because you need to create endpoints for multiple subdomains, use a [wildcard domain](#wildcard-domains) instead.
ngrok does not currently support apex domains.

## Using custom domains with TCP endpoints

Expand Down