A client's branded domain stalls for one reason more than any other: marketing assumes IT has the next move, and IT assumes marketing has sent everything they need. Nothing is technically broken. The request just sits in an inbox.
This guide covers the four places a setup gets stuck, how to find out who controls the client's DNS before you promise a date, and the one request to send IT so it cannot be misread.
TLDR: Ask for one CNAME on a subdomain, send the exact hostname and target in the first message, name one person who owns the follow-up, and assign the domain to the page only after the certificate shows as active. Most delays sit in the handoff, so a follow-up schedule fixes more than any DNS trick.
The four places a client's custom domain gets stuck
Here is where we see setups stall, in the order they happen.
| Stage | What goes wrong | What it looks like |
|---|---|---|
| Request | IT gets "please point the domain to our new tool" with no hostname or target | A reply asking what to do, three days later |
| DNS record | The wrong record type, a record on the bare root, or a typo in the target | Domain never resolves to your page |
| Certificate | The record is right but the certificate is not issued yet | Status stays Pending, browser shows a warning |
| Assignment | The domain is verified but not attached to the portal or link page | Domain loads a blank or default page |
Find your stage first. Each one has a different fix, and most agencies keep re-sending the same email to fix a problem that is two stages further along.
Find out who controls the client's DNS before you promise a date
The person who approved the project is rarely the person who can edit the zone. Before you give the client a go-live date, ask three things:
- Who manages the domain's DNS? It might be an IT team, a web agency from three years ago, or the founder's registrar login that nobody can find.
- Where is it hosted? The registrar (GoDaddy, Namecheap and so on) and the DNS host can be different companies.
- Is a proxy or security layer in front of it? A proxy at the DNS host can stop the certificate from being issued.
If the answer to the first question is "we are not sure", stop and solve that first. Recovering a lost registrar login can take longer than the whole setup.
Send IT one request that cannot be misread
IT teams treat every unclear request as a security ticket. Make yours small and exact. Copy this and fill in the blanks:
Please add one DNS record for our social media tools. Type: CNAME. Name: portal (so the address becomes portal.clientname.com). Target: the hostname we give you below. Leave all other records as they are. Reply to me when it is saved and I will confirm it on our side.
Three details matter here:
- Use a subdomain. A CNAME cannot be placed on the root domain, and asking IT to touch the root domain makes the request feel risky.
- Say what you are not asking for. "Leave all other records as they are" removes the biggest worry on their side.
- Ask for a reply, not silence. A saved record without a message tells you nothing.
Records usually take minutes to a few hours to be visible. Allow up to a day or two before you assume something is wrong.
Why the certificate stays on Pending after the record is correct
This is the stall that frustrates everyone, because DNS looks right. The platform has to see the record before it can issue the certificate for the domain, so check these in order:
- The hostname matches exactly. One extra letter or a pasted trailing space is enough.
- No proxy sits in front of the record. If the DNS host proxies traffic, set the record to DNS only until the certificate is issued.
- No CAA record blocks the issuer. Some security teams add these years ago and forget them.
- Enough time has passed. Give it a few hours before you escalate.
Our walk-through of what to check when a custom domain SSL fails goes deeper on each of these.
Assign the domain to the page last, and give the follow-up an owner
Attach the domain to the client's portal or link page only once the status says active. Doing it earlier is how a verified domain ends up showing a 404.
If you run client portals or link-in-bio pages on Mydrop, the domain's status and certificate state are visible on your side, so you can tell IT exactly what is missing rather than guess. See how the client portal and link-in-bio pages use a brand domain, and why clients ask for one in why agency clients need their own custom domain.
Then put dates on it:
| Day | Action | Owner |
|---|---|---|
| 0 | Send the request with exact hostname and target | You |
| 2 | Ask for a one-line status | You |
| 5 | Offer a 15-minute call with IT, screen shared | You |
| After record saved | Confirm status, assign the page, test on a phone | You |
Next step: open the last client whose domain is still pending, work out which of the four stages it is stuck in, and send the request above with the exact hostname filled in today.
Google review
Trustpilot review
Product Hunt comment
