Connect a Netlify domain
Put a custom domain from Netlify on your app with automatic HTTPS. One-click (OAuth) setup, the exact DNS records, and how to verify it went live.
Connect a Netlify domain
Setup type: One-click (OAuth). You sign in to Netlify in a popup and approve the change. No records to copy; no password is shared with the app.
Netlify supports native OAuth: sign in to Netlify, approve, and the records apply. The same Netlify bearer that authorizes the connection drives the Netlify DNS API, so it's a genuine one-click path for domains hosted on Netlify DNS.
What you'll need
- A domain whose DNS is managed at Netlify.
- Access to your app's CustomDomain dashboard (it shows the exact target for your account).
The records
CustomDomain gives you the authoritative records for your account in the dashboard, typically a CNAME (or apex A/ALIAS) pointing your domain at the edge. Use the values shown there; the shape is always the same, the target is per-account. There is no separate ownership TXT to add on this path: control is proven by the rail itself, or by the records appearing in your own authoritative DNS. See Setup types.
Setting it up on Netlify
- In the connect widget, choose Netlify and click connect.
- A Netlify sign-in window opens. Approve the requested DNS change.
- The records apply automatically; you're returned to the app, which verifies and goes live.
Netlify specifics
- The Netlify token is a full-account token (no granular scopes), like DNSimple.
- This works only when the domain's nameservers are delegated to Netlify DNS. If the domain still uses your registrar's nameservers, use the guided-manual path instead, the write has to happen where the domain actually resolves.
- Native Netlify OAuth (full-account token, no granular scopes, like DNSimple); the same bearer drives the Netlify DNS API. DNS writes require the domain's nameservers delegated to Netlify DNS.
How you know it worked
CustomDomain polls public DNS and issues the TLS certificate automatically. When the dashboard shows the domain live, HTTPS is serving. Drift monitoring then watches the records so a later change at the provider doesn't silently break the domain.
FAQ
My domain is registered elsewhere but I use Netlify. Does one-click work?
Only if you've delegated the domain's nameservers to Netlify DNS. If DNS still resolves at your registrar, connect it there (or via the manual records) instead.
Related
- All DNS providers, the full connection catalog.
- How custom domains work
Connect a Namecheap domain
Put a custom domain from Namecheap on your app with automatic HTTPS. Guided manual setup, the exact DNS records, and how to verify it went live.
Connect a Amazon Route 53 domain
Put a custom domain from Amazon Route 53 on your app with automatic HTTPS. Automatic (API token) setup, the exact DNS records, and how to verify it went live.