Domains, DNS and SSL Explained for First-Time Builders
Domains, DNS and SSL explained in plain English: what each one does, how they connect your site to its name, and the mistakes first-time builders make.
7 min read

You've built a site, it's live on a free link like my-site.vercel.app, and now you want a real name for it. This is the point where a lot of first-time builders hit a wall of jargon: registrars, nameservers, A records, CNAMEs, SSL certificates.
It's less complicated than it sounds. There are really just three ideas, and once you understand how they fit together, connecting a domain takes about 15 minutes. Here are domains, DNS and SSL explained, using the setup behind spen10.com as a real example.
The three pieces
- A domain is the name, like
spen10.com. You don't buy it forever. You rent it, usually a year at a time, from a company called a registrar. - DNS (Domain Name System) is the internet's address book. It turns a name people can remember into the address of the server that actually has your site.
- SSL (technically TLS these days, but everyone still says SSL) is what puts the
https://and the padlock in the browser. It encrypts the connection, so nobody in between can read or tamper with what's sent.
Here's how they work together when someone visits your site:
Registrar, DNS provider and host: three different jobs
This is the part that confuses people most: three different companies can be involved, and they don't have to be the same one.
- Registrar: where you rent the domain.
- DNS provider: where your DNS records live. Often it's your registrar by default, but it doesn't have to be.
- Host: where your site's files and code actually run.
For spen10.com, the DNS is managed in Cloudflare and the site is hosted on Vercel. That's a common setup, and it works well. The key thing to know is where your DNS lives, because that's where you'll make changes. If you edit records at your registrar while your DNS actually lives somewhere else, nothing happens, and that's a very confusing afternoon.
The DNS records you'll actually use
A DNS record is one line in your domain's address book. There are many types, but these four cover nearly everything a first-time builder needs:
- A record: points a name to an IP address (a server's numeric address). Often used for the root domain, like
spen10.com. - CNAME record: points a name to another name. Often used for subdomains, like
www.spen10.compointing at an address your host gives you. - TXT record: holds a bit of text. Used to prove you own a domain and to set up email authentication.
- MX record: says which service receives email for your domain.
Notice that your website and your email are separate. Changing records for your site won't affect email, as long as you leave the MX and email-related TXT records alone. Deleting records you don't recognize is the fastest way to break your email.
Connecting a domain to your host, step by step
Every host works a little differently, but the steps for Vercel are typical:
- Add the domain to your project. In your project's domain settings, type in your domain. Vercel will usually suggest adding both the root (
yourdomain.com) andwww, with one redirecting to the other. - Copy the records it shows you. Your host will tell you exactly which records to add and their values. Use the values it shows you, not ones from a tutorial (including this one), because they can change.
- Add them at your DNS provider. Log in wherever your DNS lives and create those records.
- Wait for it to verify. DNS changes often work within minutes, but they can take a few hours to spread everywhere. Each record has a TTL (time to live) that controls how long other computers cache the old answer.
- Let the host handle SSL. Once the domain points to Vercel, it issues and renews a free SSL certificate automatically. You don't need to do anything.
If your DNS is on Cloudflare, one extra detail: each record has a proxy toggle. An orange cloud means Cloudflare sits in front of your site. A grey cloud means "DNS only". For spen10.com, the Vercel records are set to DNS only, because Vercel already handles the speed and security side, and its docs recommend against putting another proxy in front of it.
SSL: you probably don't need to buy it
Ten years ago, SSL certificates often cost money and had to be installed by hand. Today, free certificates from Let's Encrypt are the norm, and most modern hosts (Vercel, Netlify and others) set them up and renew them for you.
So if your registrar tries to sell you an SSL certificate at checkout, for a typical site on a modern host, you can skip it.
Mistakes first-time builders make
- Letting the domain expire. Turn on auto-renew and keep your payment details current. Expired domains can be bought by someone else.
- Editing DNS in the wrong place. Check where your domain's nameservers point. That's where your records live.
- Breaking email. Leave MX and email TXT records alone unless you know what they do.
- Panicking too early. If it doesn't work after five minutes, give it an hour before changing things again.
- Buying every upsell. Most sites need just the domain. Privacy protection is worth having (and often free); most other add-ons aren't.
To check what a domain points to right now, you can run this in a terminal on Windows, Mac or Linux:
nslookup yourdomain.com
And if you haven't launched yet, start with going from idea to deployed website in a weekend. Adding the domain is the last step, and now you know what's going on behind it.
— Spencer
Share this post
Found this useful?
Get the next one in your inbox. No spam, unsubscribe anytime.
