What Is Domain Connect?

Why it matters

The hardest step in connecting a domain to any service is usually the DNS change. People end up in an unfamiliar registrar dashboard, unsure which record to edit, and a typo can take the site offline. Support teams see the same questions over and over: which host field, should it be @ or blank, why the old A record is still there.

Domain Connect removes that step. The service and the DNS provider agree on a template ahead of time, and you only have to click approve.

How it works

1. The service publishes a template describing the records it needs, for example an A record on the apex and a CNAME on www.
2. The DNS provider reviews and accepts the template.
3. When you connect a domain, the service checks whether your nameservers belong to a supporting provider.
4. If they do, you’re sent to the provider, you log in and confirm, and the records are written.
5. If they don’t, you get the manual instructions instead.

Common mistakes

• Assuming every registrar supports it. Many don’t. Always have a manual fallback.
• Forgetting conflicting records. A template can replace the old A record, but a stray AAAA record can still send some visitors to the wrong place.
• Mixing it up with registrar forwarding. Domain Connect only writes DNS records. The redirect itself still has to be served somewhere, with HTTPS.

Domain Connect and Domain Forward

Today you set up Domain Forward by adding an A record (138.68.125.144) or a CNAME (edge.domain-forward.com) at your registrar. The DNS setup guide walks through it. We’re working on one-click DNS setup with Domain Connect and a Cloudflare API token flow, so you won’t have to copy values at all.