Connect a Netlify domain
Connect a Netlify domain with one click.
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: a CNAME for a subdomain such as www, and A records for a root domain (Netlify DNS has no ALIAS or flattened CNAME at the root). 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
- Enter the domain in the connect flow (the console, or the widget inside the product you're connecting to). It detects Netlify and offers to sign in with Netlify.
- A Netlify sign-in window opens. Approve the requested DNS change.
- The records apply automatically; you're returned to the app, which usually verifies them within seconds and goes live.
Netlify specifics
- The Netlify token is a full-account token (no granular scopes), like DNSimple.
- This works only when the domain has a DNS zone in your Netlify account and its nameservers are delegated to Netlify DNS. If it does not, CustomDomain™ says "is not on Netlify DNS" and what to do. The write has to happen where the domain actually resolves: connect it at that provider, or use the guided-manual path.
- Every team you belong to is searched for the zone, so you do not pick a team.
- Records Netlify manages for a site (the
NETLIFYrecords it adds when you assign a domain to a site) are never changed. If the name you are connecting is still assigned to a Netlify site, remove it from that site first or use a different name. - If the sign-in stops working, for example after a Netlify password reset (which ends every Netlify sign-in), connect Netlify again.
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