Connect your own domain
Your site can live at your own address — drsangeetha.com rather than a Puko one. You add a single record at whoever you bought the domain from, and we do the rest.
What you need
- A domain you already own.
- The login for wherever you bought it.
- About ten minutes, then a wait — usually minutes, sometimes an hour.
How it works
- You enter your domain in Settings, and we ask a certificate authority for an HTTPS certificate in your name.
- They give us one record to prove you own it. We show it to you.
- You add that record at your registrar. This is the only manual part.
- We take it from there — the certificate is issued and hosting is set up automatically. Your site starts answering on your domain.
The one thing people get wrong
Enter only the part before your domain. Most panels add the domain for you, so pasting the full name creates a record like _abc.example.com.example.com — which never resolves and looks exactly like a record that has not propagated.
If you have added the record and it still is not verifying an hour later, this is almost always why.
Find your registrar
The record is the same everywhere. Only the buttons differ.
Where the records actually go
Not always where you bought the domain. If you have ever pointed it at another service — Cloudflare, a web host, a page builder — that service answers for it now, and the record has to be added there instead.
Puko works this out for you: the Domain Connect Help form sends us the nameservers currently answering for your domain, so we can tell you which panel to open.
While you wait
DNS changes spread at their own pace. Usually a few minutes, sometimes up to an hour, occasionally longer if your provider caches heavily.
Do not keep changing the record while waiting. Each edit restarts the clock, and it is the most common reason a connection that would have worked takes all afternoon. Add it once, press Check, and leave it.
If it will not connect
Open your site’s Settings and use Domain Connect Help. It sends us your domain, its current state, what public DNS servers are answering, and who runs your zone — so we can look at the actual problem rather than asking you to describe it.
