How to Set Up a Custom Domain in 10 Minutes (Step-by-Step)
DOMAIN STATUS: READY TO CONNECT_
Set up a custom domain in 10 minutes
Instead of sending visitors to yourwebsite.hostingprovider.com, you can use a professional address like www.yourbusiness.com. For most websites, the basic process takes around 10 minutes once you have access to your domain and hosting provider.
Domain
The address people use to reach your site — e.g. yourbusiness.com.
Hosting
The server where your site's files and app actually live.
You can buy both from the same provider, or manage them separately.
Before you start
- A registered domain name
- Access to your domain's DNS settings
- A hosted website or web application
- The DNS records your hosting provider requires
- Access to your hosting account
The 10 steps
Buy or choose your domain
Already own one? Skip ahead. Otherwise register it, then open your registrar's DNS Management or Manage DNS section — you'll mainly need A and CNAME records for a website connection.
Find your host's DNS instructions
Log in to your hosting platform and look for Domains → Add Domain or Settings → Custom Domain. It should display the exact records you need — don't reuse example values from a guide.
Add the A record
If your host gives you a server IP, add:
@ represents your root domain — example.com.
Add the www CNAME record
To make both example.com and www.example.com work:
Save your DNS records
Double-check before saving — and don't delete records you don't recognize. Your domain may already carry MX, TXT, SPF, DKIM, DMARC, or third-party verification records that other services depend on.
Add the domain to your host
Enter the domain in your hosting platform's custom domain field. A message like "Domain verification pending" right after saving DNS is normal.
Wait for propagation
Sometimes it's live in minutes; sometimes longer, depending on TTL, caching, and resolvers. Avoid changing records repeatedly while you wait — it only makes troubleshooting harder.
Enable HTTPS
Most hosts issue an SSL/TLS certificate automatically once the domain is verified. If it doesn't appear right away, check that DNS is correct, the domain is verified, and your host supports auto-SSL.
Test both versions
Check example.com, www.example.com, and their HTTPS versions. Ideally your preferred version loads the site and the other redirects to it.
Test the whole site
Homepage, navigation, forms, images, CSS/JS, login, API calls, payment pages, mobile layout, HTTPS, and the www/non-www redirect.
A record vs. CNAME
A record
Points a domain to an IPv4 address.
CNAME
Points one hostname to another. Common for subdomains.
Subdomains
The same idea extends to app., api., or blog. subdomains:
Cloud hosting vs. a VPS
Cloud platform
Add the domain in your host → copy its DNS records → add them at your registrar → verify → enable HTTPS → test.
VPS
Point A @ and A www at your VPS's IP, then configure the web server (Nginx, Apache, Caddy, Docker, Node, Laravel…) to respond to that domain — DNS only tells browsers where to go.
Common problems
"Domain not connected"
Wrong IP, missing CNAME, or verification/propagation still in progress.
Fix: compare your records against the exact values your host provided.
DNS_PROBE_FINISHED_NXDOMAIN
The domain isn't resolving. Check the A record, CNAME, nameservers, spelling — and that the domain hasn't expired.
HTTPS not working
Works on HTTP but not HTTPS usually means SSL hasn't issued yet. Check verification, DNS, and SSL status before installing a certificate manually.
www works, root doesn't (or vice versa)
Check the A record on @ or the CNAME on www — and watch for a conflicting record on the same hostname.
Email stopped working
Usually caused by replacing nameservers or deleting MX/TXT/SPF/DKIM/DMARC records. Never remove email records just to connect a website.
Changed DNS but nothing happened
Caching is likely. Confirm the record is correct, check your host's domain status, test from another network, and give it time before changing anything else.
FAQ
How long does connecting a domain actually take?
Configuration itself is about 10 minutes; propagation and SSL issuance can take longer depending on your provider.
Do I need hosting to use a custom domain?
Yes — a domain and hosting are separate services, and you need somewhere to host the site the domain points to.
Can my registrar and host be different companies?
Yes. You just configure DNS at the registrar to point to your hosting platform.
A record or CNAME — which do I use?
Whichever your hosting provider specifies. A records point to an IP; CNAMEs point to another hostname.
Will changing DNS delete my website?
No — it changes where the domain points, not your files. Incorrect changes can make the site or email temporarily unreachable, though.
Does a custom domain help SEO?
It gives a professional identity, but rankings depend on content, technical SEO, performance, and relevance — not the domain alone.
Final checklist
- Domain is registered
- DNS settings are accessible
- Correct A/CNAME records are configured
- Existing email records are preserved
- Domain is added to the hosting platform
- DNS verification is successful
- HTTPS/SSL is active
- Root domain and www both work, with redirects correct
- Site loads on mobile, forms and functionality work