Connect a custom domain to your website: DNS and SSL setup, common errors and who to call
Short answer: Connecting a custom domain means adding a few records in your domain's DNS settings (DNS, the Domain Name System, is the address book that tells browsers which server hosts your site). You add an A record or CNAME that points your name to the website host, and the host then issues an SSL certificate, the padlock that makes the address start with https. Change only the web records, never the mail records, and allow up to 24 hours before you assume something is broken.
You bought a domain, you need it to open your website with a padlock, and you do not want to break your email or sit through a week of error pages.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
The process has four parts: decide where DNS lives, add the records your website host gives you, wait for the check and the certificate, then test. Most failures come from a wrong record type, a typo, a proxy or a leftover record from the old host. The steps below are written for a non-technical owner, with the exact checks to run at each point and a table of what each record should look like.
The worked example uses Ploy, an AI platform that builds and hosts websites from a chat, because its docs spell out the records and statuses. I earn a commission if you sign up through that link. The same ideas apply to most hosts, but copy the values from your own host's dashboard, not from this page.
This page may contain affiliate links from which Blur Studio earns commissions.
The words you need, in plain English
- Registrar: the company where you bought the domain (for example GoDaddy, Namecheap or Cloudflare Registrar).
- Nameservers: the servers that hold your DNS records. Whoever runs your nameservers is where you edit records.
- A record: points a name to an IPv4 address, a string of numbers that identifies a server.
- CNAME record: points a name to another name, such as
wwwto your host's address. - TXT record: holds text. It is used to prove you own a domain and to set up email security.
- MX record: tells the internet where your email is delivered. Do not touch it when you connect a website.
- CAA record: lists which companies may issue certificates for your domain.
- TTL: how long, in seconds, other computers remember a record before checking again. Cloudflare's docs say Auto means 300 seconds, and DNS-only records can be as low as 60 seconds on non-Enterprise plans.
- Apex (root) domain:
example.com. www:www.example.com. They are different names with their own records. - SSL certificate: the file that lets your site load over https.
Before you touch anything: protect your email
This is the step most guides skip. Changing the wrong records can stop your email the same day.
- Open your DNS settings and take a screenshot or export of every record. Save it.
- Look for MX records and TXT records beginning
v=spf1, or names like_dmarcorselector._domainkey. They belong to email. Leave them alone. - Change only the A record for the apex (
@) and the CNAME forwww, plus any verification records your host asks you to add. Do not choose "reset to default" and do not paste in a whole zone. - Do not change the nameservers unless your host tells you to. Ploy's docs say it does not take over your DNS or nameservers, you add the records it gives you. Changing nameservers to a new provider can drop mail records unless you copy them across.
- If you use Google Workspace, the correct mail record is an MX pointing to
smtp.google.com(older accounts may use legacy values, still supported). Google says keeping old or incorrect MX records can break mail, and that new MX records can take up to 72 hours to be recognised. - If you use Microsoft 365 or another sender, keep only one SPF record (a TXT record starting
v=spf1) per domain. Microsoft's docs say several SPF records cause an error and that SPF allows at most 10 lookups.
Step by step: connecting a domain (Ploy example)
- Check your plan. As of November 2026 Ploy's Free plan allows 0 custom domains, Starter 1, Pro 5 and Enterprise unlimited. The apex, www and subdomains of one domain count as one. See Ploy pricing.
- Publish your site first. The setup says "Publish your site first" if you have not.
- Open the site, then Domains, then Add domain. Choose "Set it up with Ploy" (this uses credits) or "Set it up yourself" and enter your domain.
- If the domain already shows another site, choose whether to replace all pages, keep some pages elsewhere, or take only some pages from this site.
- Connect. Use the automatic Entri connection if your registrar is supported, or choose "Add the records yourself".
- Add the verification records first. Ploy says to add the
_acme-challengeCNAME records (they prove ownership for the certificate and do not affect live traffic) before the others. Its DNS page also says to confirm the certificate with Ploy support before you switch the live records. The values are shown in your dashboard and in Ploy's DNS setup page. Copy them from there. The hash in them can be specific to your setup. - Wait for the certificate message, then add the live records. As of November 2026, Ploy's DNS setup page (last updated 10 November 2026) shows an A record for
@pointing to207.207.209.209and a CNAME forwwwpointing toproxy.runploy.com. Do not treat that address as permanent. Use what your dashboard shows. - Set Cloudflare records to DNS only (grey cloud) if you use Cloudflare.
- Press Check records. Ploy rechecks every 30 seconds. The status moves through Check DNS records, Issue SSL certificate and Go live.
Registrar quirks: if your registrar cannot make a CNAME on the apex, use the A record. Some want the name left blank instead of @. Some need a trailing dot after CNAME values and some add or reject it. Ploy's page suggests a TTL of 60 to 300 seconds while you set up.
What each record should look like
| Type | Name | Should point to | Notes |
|---|---|---|---|
| CNAME | _acme-challenge and _acme-challenge.www | Value from your host's dashboard | Add first. Safe for live traffic. |
| A | @ (apex) | Host's IP address from the dashboard | Use if root CNAME is not allowed |
| CNAME | www | Host's address from the dashboard | Cannot sit beside other record types on the same name |
| MX | @ | Your mail provider | Do not change |
| TXT | @ (SPF, verification) | Your mail and tool providers | Do not change. Only one SPF record. |
| CAA | @ | Must allow the host's certificate issuer | Ploy's docs say to allow Google Trust Services if you use CAA |
How long it takes, and the sources that disagree
DNS changes are not instant. Ploy says waiting for DNS can take up to 24 hours, and that certificate issuing usually takes a few minutes after DNS verifies. Google says new Workspace MX records can take up to 72 hours to be recognised and SPF up to 48 hours to work. Web articles often say 24 to 48 hours. These are different records and different companies, so each figure applies to its own case. For a web record on Ploy, plan for a day. For mail changes, plan for up to three.
To reduce downtime, lower the record TTL a day ahead of a move on a live site. Ploy's migration guide says to set it to 300 seconds. Google's hosting-move guide says a conservative low value, for example a few hours, at least a week before. They differ, so pick one and be consistent. Add the verification records first and leave the live A and www records pointing at the old host until the certificate is ready.
How to check what the internet sees
- Use a free DNS lookup website, such as whatsmydns.net, which Ploy's docs point to, to see the record from several places.
- On a Mac or Linux terminal, general commands are
dig A example.com +short,dig CNAME www.example.com +short,dig MX example.com +shortanddig caa example.com +short. On Windows,nslookup -type=TXT example.comworks. - Test on a phone using mobile data, which uses a different network from your office Wi-Fi and a different cache.
- Look at the padlock. Click it, then view the certificate and the issue date.
Pass: the lookup shows the value your host gave you, the status says Live, and https opens with a padlock on both example.com and www. Fail: the lookup shows an old value, nothing, or two conflicting records.
Common errors and fixes
| What you see | Likely cause | Fix |
|---|---|---|
| Stuck on Connecting | Wrong record type (an A where a CNAME is needed), a typo, or unsaved changes | Compare each record with the dashboard, save, then press Check again |
| Misconfigured, flickering | Latest lookup does not point to the host | Fix the record; it can flip while old values expire |
| Live but you still see the old site | Cache in your browser, computer or internet provider | Test on mobile data, flush the DNS cache. Ploy says not to roll back DNS if the status is Live |
| Certificate will not issue | DNS not verified, or a CAA record blocks the issuer | Check dig caa; allow the host's issuer; press Check again; wait up to 24 hours |
| Too many redirects | Conflicting redirect rules at the registrar or CDN, or Cloudflare Flexible SSL | Remove the extra rules; use Full (strict) or DNS only |
| Cloudflare error 1001 right after the change | Records just pointed | Press Check again |
| Cloudflare error 1034 | Another Cloudflare-hosted service still holds the name | Remove the hostname there first |
| Moving from Webflow | Domain still connected there | Remove it in Webflow's publishing settings at least 5 minutes before verifying |
| Browser says not secure on one page | Mixed content: the page loads images or scripts over http | Change those addresses to https and republish |
On Cloudflare, Cloudflare's docs explain that Flexible SSL encrypts visitor to Cloudflare but not Cloudflare to your server, and redirect loops occur if the origin forces http to https. Its fixes are to remove the origin redirect, choose Full or higher, or enforce https at Cloudflare's edge. Ploy's custom domains page (last updated 12 November 2026) says to use DNS only (grey cloud, meaning Cloudflare passes traffic through without its proxy) for its records and says Flexible mode causes conflicts. You can also purge Cloudflare's public DNS cache for the root and www records on its purge page.
Apex, www and your preferred address
Pick one version as your main address. In Ploy, the apex and www share one row, and "Set as primary domain" in the row menu chooses which one is canonical; the other forwards to it with a permanent 308 redirect. Publish again after changing so canonical tags and the sitemap update. To move a domain to another Ploy site, use "Move to another site" rather than removing it first. Removing a domain causes immediate downtime and deletes its path routing, though Ploy does not delete your DNS records.
If the domain is replacing an older live site, plan for search traffic too. Read what to do if rankings drop after a migration and keeping SEO rankings when you move a site.
When to stop waiting and who to call
- After 24 hours with records matching the dashboard and still not Live: contact the host. Ploy's docs say to email support@ploy.ai for DNS and domain issues, and also list Private support in the dashboard (for billing, hosting, domains and access). Ploy publishes no response time.
- If the lookup shows records that do not match what you set: contact your registrar or DNS provider. They control the records.
- If email stopped: restore the MX and TXT records from your screenshot first, then call your mail provider.
- If the domain is locked or expired: contact the registrar.
- If your site uses a CDN or security tool you do not recognise: ask whoever set it up before changing records.
Send support these items: your domain, the host name of the site, a screenshot of the DNS records, a screenshot of the status, and the time you made the change.
Copy-ready checklist
- Screenshot all current DNS records.
- Confirm your plan allows a custom domain.
- Publish the site on the host first.
- Lower the TTL a day ahead if the site is live elsewhere.
- Add the verification (certificate) records first.
- Check for a CAA record and allow the host's issuer if one exists.
- Add the A and www records from the dashboard, nothing else.
- Cloudflare: DNS only, and SSL mode Full (strict) if you proxy anything.
- Press Check, then wait up to 24 hours.
- Test on mobile data: apex, www, https, and one inner page.
- Send a test email to and from your domain.
- Set the primary version, republish, and resubmit the sitemap in Google Search Console.
How I'd approach this
I would treat DNS as two small jobs: web records and mail records, and only ever edit the first. I would also do it on a quiet weekday morning, not on a Friday, so someone can fix a problem. Take the screenshot, add the verification records, wait for the certificate, then switch the live records. If you are choosing a platform, ask how many domains your plan allows and what happens if you remove one. Ploy's Free plan lets you build and publish to a ploy.build address first, then add a domain on a paid plan, so you can test the site before you spend. Before you move a domain that carries live search traffic, read the migration pages linked above.
If your domain setup is part of a bigger problem, such as a site, a booking flow and a CRM that must all work together, Blur Studio builds and cares for the custom version; see what that includes. For other launch problems see the form fix checklist, for a slow site after launch, page speed problems on marketing sites, and for how other hosts do it, connecting a custom domain to Netlify.
First-week plan:
- Day 1: log in to the registrar, confirm you own the account, screenshot all records and list where email is hosted.
- Day 2: build and publish the site on the host's free address and review every page.
- Day 3: add the verification records and wait for the certificate.
- Day 4: add the live records, press Check, test on mobile data and send test emails.
- Day 5: set the primary address, republish, submit the sitemap, and note the renewal date of the domain in your calendar.
You may also want adding landing pages to an existing website without moving your domain.
Questions people ask
How do I connect a custom domain to my website?
Publish the site, open your host's domain settings, add the domain, then add the DNS records the host gives you at your registrar: verification records first, then the A and www records. Wait for the host to verify and issue an SSL certificate. Copy values from your own dashboard.
How long does DNS take to update?
It varies. Ploy says waiting for DNS can take up to 24 hours. Google says new Workspace MX records can take up to 72 hours and SPF up to 48 hours. Web articles often say 24 to 48 hours. Test from mobile data to avoid your own cache.
Why is my SSL certificate not working?
Usually DNS is not yet verified, a CAA record blocks the certificate issuer, or a proxy such as Cloudflare in Flexible mode is interfering. Check records against the dashboard, run a CAA lookup, set Cloudflare to DNS only, then press Check again.
Will connecting a domain break my email?
Not if you only change the A record, the www CNAME and verification records. Email depends on MX and TXT records. Screenshot them first and never reset the whole zone. Changing nameservers can drop them unless you copy every record.
Why do I see too many redirects?
Often a conflict between redirect rules at your registrar, CDN or host, or Cloudflare Flexible SSL while the origin forces https. Remove the extra rules and use Full (strict) or DNS only. Cloudflare documents this loop.
What is the difference between an A record and a CNAME?
An A record points a name to a numeric address. A CNAME points a name to another name. Most hosts want an A record on the apex (example.com) if your registrar cannot do a root CNAME, and a CNAME on www.
Does Ploy manage my DNS?
No. Ploy's docs say it does not manage your DNS or take over nameservers: you add the records it provides at your registrar. A custom domain needs a paid plan. See Ploy and its pricing.
Who do I call if my domain still does not work?
Call your host if your records match its dashboard after 24 hours, your registrar if the live lookup does not match what you set, and your mail provider if email stopped. Send a screenshot of the records and status.
More in this topic: Websites: fixing migration, DNS, forms, speed and CRM problems (6 guides) →