The problem DNS solves
Computers don't understand names like sysvyn.com. What they understand are numbers — specifically, IP addresses, which look something like 104.21.45.67. Every website, every server, every device connected to the internet has one of these numerical addresses.
The problem is that humans are terrible at remembering strings of numbers but very good at remembering names. You can remember sysvyn.com. You can't realistically remember 104.21.45.67 for every website you visit.
DNS — the Domain Name System — is the solution. It's a global database that translates human-readable names into the numerical IP addresses that computers need to connect.
Before smartphones, you'd look up a person's name in a phone book to find their number. DNS works exactly the same way — you give it a name (sysvyn.com) and it gives you back the number (104.21.45.67) so your computer knows where to connect. The difference is that DNS does it in under 100 milliseconds, automatically, every time you visit a website.
How the lookup actually works
When you type a web address and press Enter, a surprisingly sophisticated process happens — all before your browser loads a single byte of the page.
-
1Your computer checks its own memory first
Your device keeps a local cache of recent DNS lookups. If you visited sysvyn.com an hour ago, your computer probably still remembers the IP address and skips the rest of these steps entirely.
-
2It asks your DNS resolver
If the answer isn't cached, your computer asks a DNS resolver — usually run by your internet provider or a service like Cloudflare (1.1.1.1) or Google (8.8.8.8). This resolver is your primary contact for DNS queries.
-
3The resolver works up the chain
If the resolver doesn't have the answer cached, it asks a Root Name Server — one of 13 sets of servers worldwide that know which servers are responsible for each top-level domain (.com, .co.za, .net etc.).
-
4The authoritative answer comes back
Eventually the query reaches the authoritative name server for that specific domain — in Sysvyn's case, Cloudflare's nameservers. That server has the definitive answer and returns the IP address.
-
5Your browser connects
Your computer now has the IP address, stores it in cache so it doesn't have to look it up again for a while, and your browser connects to the website. The whole process typically takes 20–120 milliseconds.
This is why changing DNS settings — like pointing your domain to a new host — takes time to "propagate." The change has to ripple through cached records worldwide before everyone sees the new address. This is the 15 minutes to 48 hours wait you've probably experienced when changing domains.
DNS records — the different types
DNS isn't just one thing. A domain's DNS settings contain multiple different record types, each serving a specific purpose. Here are the ones you'll encounter most often:
| Record Type | What it does | Example use |
|---|---|---|
| A | Points a domain name to an IP address (IPv4) | sysvyn.com → 104.21.45.67 |
| CNAME | Points a name to another name (an alias) | www.sysvyn.com → sysvyn.com |
| MX | Tells email servers where to deliver email for your domain | hello@sysvyn.com → Zoho Mail servers |
| TXT | Stores text information — often used for email verification and security | SPF records to prevent email spoofing |
| NS | Declares which servers are authoritative for your domain | emely.ns.cloudflare.com |
When you set up a website, connect professional email, or verify your domain with Google — you're editing these DNS records. That's exactly what happened when Sysvyn pointed your domain to Cloudflare and set up your Zoho Mail MX records.
What are nameservers?
Nameservers are the servers that hold all the DNS records for your domain. When you register a domain, it comes with default nameservers from your registrar. When you move to Cloudflare for DNS management, you update those nameservers to Cloudflare's — which is why you had to go into Namecheap and change that setting.
Think of nameservers as the address of the phone book that holds your domain's listings. Changing nameservers means telling the internet "go look in this phone book instead of the old one." The propagation wait is just every DNS server worldwide updating their directions to the new phone book.
If your website ever stops loading after a DNS change, the most common causes are: propagation isn't complete yet (wait), an A record pointing to the wrong IP address, or missing records entirely. In Cloudflare, you can see all your records clearly and fix them without touching any code.
Why Cloudflare DNS specifically?
Not all DNS providers are equal. Cloudflare runs one of the fastest DNS networks in the world — their 1.1.1.1 resolver is consistently the fastest public DNS service measured globally. When your domain's DNS is managed through Cloudflare, you also get DDoS protection, analytics, and the ability to proxy traffic through their global network for security and speed.
It's also why Sysvyn uses Cloudflare for every client domain — the DNS management, security layer, and CDN are all in one place, free of charge, and significantly faster and more reliable than most hosting providers' built-in DNS tools.
Key takeaways
- DNS translates human-readable domain names into the IP addresses computers need
- The process happens in milliseconds through a chain of servers worldwide
- DNS propagation delay (15 min – 48 hours) is just cached records updating globally
- A records point domains to IP addresses; MX records route email; CNAME records create aliases
- Nameservers are the authoritative source of DNS records for your domain
- Cloudflare provides free, fast, and secure DNS management with extra protection built in
What's next
DNS gets your browser to the right server. But once you're connected, how does the website know the connection is secure? That's TLS — the technology behind the padlock in your browser. We cover that in detail in the related article below.
And if you've ever wondered what the difference between HTTP and HTTPS actually is at a practical level, that's covered in the SSL article too.