Connect a DigitalOcean domain

Setup type: One-click (OAuth). You sign in to DigitalOcean in a popup and approve the change. No records to copy; no password is shared with the app.

DigitalOcean supports native OAuth, so connecting a domain whose DNS lives in DigitalOcean is a one-click, sign-in-and-approve flow, no records to copy. This is the same DigitalOcean DNS that backs many droplet and App Platform setups.

What you'll need

• A domain whose DNS is managed at DigitalOcean.
• 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 DigitalOcean

1. In the connect widget, choose DigitalOcean and click connect.
2. A DigitalOcean sign-in window opens. Approve the requested DNS change.
3. The records apply automatically; you're returned to the app, which verifies and goes live.

DigitalOcean specifics

• The OAuth token requests read and write, DigitalOcean's granularity, which covers adding the DNS records and nothing beyond your account's 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

Does my domain need to use DigitalOcean nameservers?

Yes, the domain's DNS must be hosted at DigitalOcean (nameservers pointed to ns1/ns2/ns3.digitalocean.com) for the automatic write to land where it resolves.

Related

• All DNS providers, the full connection catalog.
• How custom domains work