guide

How to Connect a Custom Domain and Set Up Free SSL (Step-by-Step DNS Guide)

How to Connect a Custom Domain and Set Up Free SSL (Step-by-Step DNS Guide)
NC 7 min read

To connect a custom domain, you add the domain in your hosting platform, then point your DNS at it: an A record for the apex domain (example.com) and a CNAME for subdomains (www.example.com). Once DNS resolves, a free SSL certificate is issued automatically so your site loads over HTTPS — no certificate to buy, install, or renew by hand. The whole thing usually takes a few minutes to a couple of hours, almost all of which is DNS propagation.

This guide walks through it end to end: a quick DNS primer, the exact records to add, how automatic SSL works, and how to fix the handful of things that commonly go wrong. On NevTan Cloud, you deploy a site from your Git repository, add your domain, update two DNS records, and SSL activates on its own — free, with no credit card.

 Deploy your site → add your custom domain in the platform → at your registrar, add an A record for the apex and a CNAME for www pointing to the values the platform gives you → wait for DNS to propagate → SSL is issued and renewed automatically. Then force HTTPS so every visitor gets the secure version.

What You Need

  • A deployed site — your app or website already live on a platform URL.

  • A domain name — bought from any registrar (Namecheap, GoDaddy, Cloudflare, Google/Squarespace, etc.).

  • Access to your DNS settings — the registrar dashboard, or wherever your nameservers point.

That's it. You don't need to buy an SSL certificate — free, automatic HTTPS is part of the platform.

DNS in 90 Seconds

DNS is the address book that maps your domain to a server. A few terms you'll use:

  • A record — points a domain to an IPv4 address. Used for the apex (root) domain, e.g. example.com.

  • CNAME record — points a name to another name. Used for subdomains, e.g. www.example.com → your-site.nevtan.app.

  • Apex vs. subdomain — example.com is the apex; www.example.com and app.example.com are subdomains.

  • Nameservers — where your domain's DNS is actually managed. If they point to Cloudflare, you edit records in Cloudflare, not the registrar.

  • TTL — how long records are cached. Lower it before a change for faster updates.

  • Propagation — the time for a DNS change to spread across the internet: often minutes, up to ~48 hours worst case.

Key takeaway: Apex domains use an A record; www and other subdomains use a CNAME. That one rule prevents most custom-domain mistakes.

Step-by-Step: Connect Your Domain

  1. Deploy your site first. Make sure it's live on its platform URL before attaching a domain — push to deploy, confirm it loads, then add the domain.

  2. Add the domain in the platform. In your project settings, add example.com (and www.example.com if you want both). The platform shows you the exact DNS values to use.

  3. Add the DNS records at your registrar. Log in to wherever your DNS is managed and create the records the platform specified (see the table below).

  4. Verify the domain. The platform checks that DNS resolves to it — this flips from "pending" to "verified" once records propagate.

  5. Let SSL issue automatically. Once verified, a certificate is provisioned for your domain and HTTPS goes live — no action needed.

  6. Force HTTPS. Enable the redirect so http:// visitors are sent to https://, and every request is encrypted.

The documentation has the exact record values and per-project steps.

The DNS Records You'll Add

Record type

Host / name

Points to

Used for

A

@ (apex)

The IPv4 address the platform shows

example.com

CNAME

www

The target hostname the platform shows (e.g. your-site.nevtan.app)

www.example.com

Notes:

  • Use the platform's exact values — don't copy an IP or hostname from another guide; they're account-specific.

  • @ means the apex in most registrars (some call it "root" or leave the host blank).

  • Delete conflicting records — remove any old A or CNAME on the same host (e.g. a parked-page record) so yours takes effect.

Apex vs. www — Serve Both

Most sites should answer on both example.com and www.example.com. Add both in the platform, create the A record for the apex and the CNAME for www, then pick a primary and redirect the other to it (apex → www, or www → apex — either is fine, just be consistent). This avoids duplicate-content issues and makes sure every visitor lands on the canonical, secure URL.

How Free SSL Actually Works

You used to buy an SSL certificate and install it by hand. Now it's automatic and free, via the ACME protocol (the same technology behind Let's Encrypt):

  1. Once your domain points at the platform, it requests a certificate for your domain.

  2. It proves control of the domain automatically (through the DNS/HTTP you already set up).

  3. The certificate installs, and https:// goes live.

  4. It auto-renews before expiry — you never touch it again.

This is why the only "SSL step" you take is forcing HTTPS. Keeping traffic encrypted end to end is a baseline security expectation for any site today — and with automatic certificates, there's no reason not to.

Key takeaway: Free SSL isn't a feature you configure — it's issued and renewed for you once DNS resolves. Your only job is to redirect HTTP to HTTPS.

Verify and Wait for Propagation

After adding records, confirm they're live:

  • Command line: dig example.com and dig www.example.com (or nslookup) to see what your records resolve to.

  • Online checkers: a DNS propagation checker shows how the change has spread globally.

  • Be patient with TTL: if you set a high TTL before, the old record may linger until it expires. Lowering TTL before a change speeds future updates.

If verification stays pending, it's almost always DNS — give propagation time, then re-check.

Troubleshooting

  • "SSL pending" or no HTTPS yet. The certificate issues only after DNS verifies. Confirm your A/CNAME records resolve to the platform's values, then wait — issuance follows verification.

  • Domain not resolving. Check you edited DNS at the right place (registrar vs. Cloudflare nameservers), used @ for the apex, and removed conflicting records.

  • Using Cloudflare? If you proxy (orange cloud) the record, Cloudflare terminates SSL — set the record to "DNS only" (grey cloud) during setup, or use Full (strict) SSL mode, so the platform can validate and serve your certificate.

  • CAA records blocking issuance. If you have a CAA record, make sure it permits the certificate authority the platform uses, or remove it.

  • "Not secure" / mixed content. After HTTPS is live, update any hardcoded http:// asset URLs in your site to https:// (or protocol-relative) so the browser doesn't flag mixed content.

  • Still stuck? Check the platform's status page to rule out a wider issue before deep-debugging your DNS.

Frequently Asked Questions

How do I connect a custom domain to my site? Add the domain in your hosting platform, then at your registrar create an A record for the apex domain and a CNAME for www, pointing to the values the platform gives you. Once DNS resolves, the domain goes live.

How long does DNS propagation take? Usually minutes to a couple of hours, and up to ~48 hours in the worst case. A lower TTL set before the change makes updates appear faster.

Is the SSL certificate really free? Yes. Certificates are issued and renewed automatically via the ACME/Let's Encrypt system at no cost — there's nothing to buy or manually install. On NevTan Cloud, free SSL is included with no credit card.

Do I need to renew SSL myself? No. Automatic certificates renew before they expire, so HTTPS keeps working without any manual steps.

Should I use the apex domain or www? Serve both, then redirect one to the other so visitors always land on a single canonical URL. Apex uses an A record; www uses a CNAME.

Can I use Cloudflare with a custom domain? Yes, but during setup set the record to "DNS only" (grey cloud) or use Full (strict) SSL mode so certificate validation isn't blocked by Cloudflare's proxy.

Why does my site say "Not secure" after setup? Either SSL hasn't finished issuing (wait for DNS to verify) or your pages load some assets over http://. Fix mixed-content URLs and enable the HTTP-to-HTTPS redirect.

Go Live on Your Own Domain

Connecting a custom domain comes down to two DNS records and a little patience: an A record for the apex, a CNAME for www, pointed at the values your platform shows you. SSL then issues and renews itself for free, and a single HTTPS redirect makes sure every visitor gets the secure version.

On NevTan Cloud, you deploy from Git, add your domain, update DNS, and get free, automatic SSL — no credit card required. See plans and get started, or read how the platform handles deploys from repository to live site. Repo to production.