Domain Names and DNS Explained: A Business Owner's Guide

What is a domain name?

A domain name is your website's address on the internet — the text people type into their browser to visit your site. Think of it like a street address for a building. Just as "123 High Street" tells someone where your shop is located, "yourbusiness.com" tells a browser where to find your website.

Domain names exist because computers identify each other using IP addresses — strings of numbers like 104.26.10.78. These work perfectly for machines but are impossible for humans to remember. Domain names are the human-friendly labels that map to those numeric addresses. When you type a domain name into your browser, a system called DNS translates it to the correct IP address behind the scenes.

Domain names are rented, not owned. You register a domain through a registrar (like Cloudflare, Namecheap or Google Domains) and pay an annual fee to maintain your right to use it. If you stop paying, the domain eventually becomes available for anyone else to register. This is why auto-renewal is important for any domain that matters to your business.

A domain consists of two main parts: the name (e.g., "yourbusiness") and the extension or TLD (e.g., ".com", ".co.uk", ".io"). The .com extension is the most recognised and trusted for businesses, but country-specific extensions like .co.uk are equally valid and can signal local relevance to search engines.

How DNS works

DNS stands for Domain Name System. It is often described as the phone book of the internet, and the analogy is apt. Just as a phone book translates a person's name to their phone number, DNS translates a domain name to an IP address.

Here is what happens when someone types your domain into their browser, simplified:

1. The browser checks its local cache to see if it already knows the IP address for that domain. If yes, it connects directly. If no, it asks a DNS resolver.
2. The DNS resolver (usually run by your internet provider or a service like Cloudflare's 1.1.1.1) looks up the domain. It queries a chain of DNS servers: root servers, TLD servers (.com, .co.uk, etc.), and finally the authoritative nameserver for your specific domain.
3. The authoritative nameserver responds with the IP address associated with your domain.
4. The browser connects to that IP address and loads your website.

This entire process typically takes 20-100 milliseconds. It happens invisibly every time anyone visits any website. The system handles billions of lookups per day across the global internet and is one of the most critical pieces of infrastructure that most people never think about.

Common DNS records explained

Your domain's DNS settings contain several types of records, each serving a different purpose. Here are the ones you will encounter most often:

A Record — The most fundamental DNS record. It maps your domain name directly to an IP address (the server where your website lives). When someone visits yourbusiness.com, the A record tells the browser which server to connect to. You can have multiple A records for load balancing.

CNAME Record — An alias that points one domain name to another domain name. For example, you might create a CNAME record pointing "www.yourbusiness.com" to "yourbusiness.com" so both addresses work. CNAME records are also used to connect your domain to hosting services like Cloudflare Pages, Netlify or Shopify.

MX Record — Mail Exchange records tell the internet where to deliver email for your domain. If you use Google Workspace for email, your MX records point to Google's mail servers. If you use Microsoft 365, they point to Microsoft's servers. Without correct MX records, email sent to your domain will not be delivered.

TXT Record — Text records store arbitrary text data. They are primarily used for verification (proving you own the domain when setting up services like Google Workspace, email marketing platforms or SSL certificates) and for email security (SPF, DKIM and DMARC records that help prevent email spoofing).

AAAA Record — The IPv6 equivalent of an A record. As the internet transitions from IPv4 to IPv6, AAAA records point your domain to an IPv6 address. Many modern hosting providers set these up automatically.

Domain registration vs hosting

This is one of the most common points of confusion. Domain registration and web hosting are two completely separate things, even though many companies sell both.

Domain registration is the right to use a domain name. You pay a registrar an annual fee (typically $10-15/year for a .com domain) to be the registered holder of that domain. The registrar does not host your website or handle your email. It simply maintains the record that you control that domain name.

Web hosting is the server where your website's files actually live. This is a separate service with a separate provider. You point your domain's DNS records to your hosting provider so that when someone visits your domain, they reach your website on that hosting server.

You can (and often should) use different companies for registration and hosting. Many hosting companies offer domain registration as an add-on, but this can make it harder to switch hosting providers later because your domain and hosting are tied together. Keeping them separate gives you more flexibility.

Domain transfers

You can move your domain from one registrar to another. This is called a domain transfer. Common reasons to transfer include better pricing, better DNS management tools, consolidating all your domains with one provider, or leaving a registrar with poor customer service.

The transfer process typically involves: unlocking the domain at your current registrar, obtaining an authorisation code (also called an EPP code or transfer key), initiating the transfer at the new registrar by providing the authorisation code, and confirming the transfer via email. The process takes 5-7 days and usually requires that the domain has been with its current registrar for at least 60 days.

Transferring a domain does not cause downtime if done correctly. Your DNS settings transfer with the domain. However, if your current registrar also provides your DNS hosting, you should set up DNS at the new registrar before initiating the transfer to avoid any interruption.

DNS propagation

When you change a DNS record, the change does not take effect instantly across the entire internet. This delay is called DNS propagation, and it happens because DNS responses are cached at multiple levels: your browser, your operating system, your internet provider's DNS resolver and intermediate DNS servers worldwide.

Each DNS record has a TTL (Time to Live) value that specifies how long it should be cached before checking for updates. A TTL of 3600 means the record is cached for one hour. A TTL of 86400 means it is cached for 24 hours. When you change a record, you have to wait for all those caches to expire before every visitor sees the new setting.

In practice, most DNS changes propagate within a few hours, though some changes can take up to 48 hours to reach every DNS resolver worldwide. If you know you are going to change a record, lower the TTL to 300 (five minutes) a day before making the change. This ensures caches expire quickly when you make the actual update.

Common DNS mistakes to avoid

After managing DNS for hundreds of client domains, these are the mistakes we see most often:

• Letting a domain expire accidentally. If your domain expires, your website and email stop working immediately. Worse, domain squatters can register it and demand a premium to sell it back. Always enable auto-renewal on every domain that matters.
• Incorrect MX records after switching email providers. When you move from one email provider to another, the old MX records must be replaced with the new provider's records. Getting this wrong means incoming email silently disappears or bounces. Always verify email delivery after changing MX records.
• Missing SPF, DKIM and DMARC records. Without these email authentication records, your outgoing emails are more likely to be flagged as spam. Every domain that sends email should have all three configured correctly.
• Using the registrar's default nameservers when you should not be. Many registrars provide basic DNS hosting, but their DNS infrastructure is often slow and limited. Switching to a dedicated DNS provider like Cloudflare improves resolution speed and gives you better management tools.
• Not keeping DNS login credentials secure and documented. If you lose access to your DNS management, you cannot update records, and recovering access can be a slow and painful process. Store DNS credentials in a password manager and ensure more than one person in your organisation has access.

Using Cloudflare for DNS

Cloudflare's DNS service is free, fast and feature-rich. It is the DNS provider we recommend for most businesses, and it is what we use for our own domains and our clients' domains.

Cloudflare operates one of the fastest DNS networks in the world, with a global average resolution time under 11 milliseconds. Their DNS infrastructure is distributed across over 300 cities, meaning your domain resolves quickly regardless of where the visitor is located. This speed advantage directly contributes to faster website load times.

Beyond speed, Cloudflare DNS includes built-in DDoS protection for your DNS infrastructure, DNSSEC support (which prevents DNS spoofing attacks), an easy-to-use dashboard for managing records, API access for automation, and analytics showing query volume and response times.

Setting up Cloudflare DNS involves creating a free Cloudflare account, adding your domain, and updating your domain's nameservers at your registrar to point to Cloudflare's nameservers. Cloudflare automatically imports your existing DNS records during setup, so the transition is typically seamless with no downtime.

Best practices

Follow these practices to keep your domains secure and well-managed:

1. Enable registrar lock. This prevents unauthorised transfers of your domain. Most registrars have this enabled by default, but verify it is on for all your important domains.
2. Use WHOIS privacy. Without WHOIS privacy, your name, address, phone number and email are publicly visible to anyone who looks up your domain. Most registrars include WHOIS privacy for free. Enable it on every domain.
3. Enable auto-renewal. A domain expiration can take down your entire online presence. Auto-renewal with a valid payment method on file prevents this. Set a calendar reminder to verify your payment method is current once per year.
4. Use a dedicated DNS provider. Move your DNS to Cloudflare or a similar provider for faster resolution, better management tools and improved security. Keep your domain registration at the registrar but point the nameservers to your DNS provider.
5. Configure email authentication. Set up SPF, DKIM and DMARC records for every domain that sends email. This protects your domain from being spoofed and improves your email deliverability.
6. Document everything. Maintain a record of which registrar holds each domain, when each domain expires, what DNS provider is used, and the login credentials for each service. Store this in a secure, shared location that survives employee turnover.

---