You want a website that shows up when a customer types your business name. The words they type are the domain – for example myshop.com. The domain is just an address that points to a place on the internet where your site lives. The system that translates that friendly address into a computer‑readable location is called DNS – the Domain Name System.
What DNS actually does
Think of DNS as a phone book for the internet. When you look up a name in a phone book, you get a phone number. When a browser looks up a domain, DNS returns an IP address – a series of numbers like 192.0.2.45 that tells the computer where to find the server that holds your site.
The lookup happens behind the scenes. You type myshop.com, your computer asks a DNS server, the server replies with the IP address, and the browser connects to that address. If the DNS record is wrong, the browser can’t find your site and shows an error.
Where the records live
Your domain registrar (the company where you bought myshop.com) stores the DNS records, or you can point the registrar to a separate DNS provider. Either way, the records are simple text lines that tell the internet how to reach your site.
Two of the most common record types are A records and CNAME records. They serve different purposes but both end up directing traffic.
A records – the direct route
An A record links a domain (or a subdomain) directly to an IP address. It looks like this:
`` myshop.com. IN A 203.0.113.10 ``
When a visitor asks for myshop.com, DNS returns the IP address 203.0.113.10. The browser then opens a connection to that server and requests the website files.
A records are the most straightforward way to point a domain at a server. They are used when you have a single hosting location with a static IP address. If your host changes the server IP, you must update the A record to keep the site reachable.
CNAME records – the alias shortcut
A CNAME (canonical name) record does not contain an IP address. Instead, it points one name to another name. For example:
`` www.myshop.com. IN CNAME myshop.com. ``
Here www.myshop.com is an alias for myshop.com. When a browser asks for www.myshop.com, DNS first follows the CNAME to myshop.com, then looks up the A record for myshop.com and returns the IP address.
CNAMEs are handy for a few reasons:
- Flexibility – If the underlying A record changes, all the CNAMEs that point to it automatically follow the change. You don’t need to edit each subdomain individually.
- Third‑party services – Many SaaS tools give you a domain like myshop.customservice.com. You create a CNAME that points your own subdomain (e.g., blog.myshop.com) to that service address, letting the provider manage the actual IPs.
A CNAME cannot be used for the root domain (the bare myshop.com) because the root must have an A record. Some DNS providers offer “ALIAS” or “ANAME” records that behave like a CNAME at the root, but they are technically a special feature, not a standard DNS record.
Putting it together for a small business
1. Buy a domain – Choose a name that matches your business and register it with a registrar. 2. Choose a host – This is where your website files live. The host will give you an IP address (for an A record) or a hostname (for a CNAME). 3. Set up DNS – In the registrar’s DNS settings, create an A record for the root domain that points to the host’s IP. Add a CNAME for www that points to the root, so both myshop.com and www.myshop.com work. 4. Test – Use a tool like nslookup or an online DNS checker to verify the records resolve to the correct IP. 5. Keep it simple – Only add the records you need. Extra records can cause confusion and make troubleshooting harder.
Common pitfalls to avoid
- Forgetting the trailing dot – In many DNS interfaces the domain name is entered without the final period. It doesn’t affect most providers, but understanding that the dot marks the absolute name helps when reading raw DNS files.
- Mixing record types – You cannot have both an A record and a CNAME for the same name. Decide whether the name points directly to an IP or acts as an alias.
- Neglecting TTL – TTL (time‑to‑live) tells other DNS servers how long to cache a record. A very high TTL means changes take longer to propagate. For a new site, a lower TTL (like 5 minutes) can speed up updates.
- Assuming ownership of the site – When you lease a website, you keep your domain name, but the hosting and the underlying build remain with the provider. If the lease ends, the DNS records may need to be redirected to a new host.
When a lease model matters for DNS
If you are using a lease‑based website service, the provider often manages the DNS records for you. They may ask you to point your domain’s nameservers to theirs. That gives them control over the A and CNAME records, which simplifies updates but also means you rely on the provider to keep the records correct. If you ever move to a different provider, you’ll need to change the nameservers or edit the records yourself.
Bottom line
A domain is your address. DNS is the phone book that translates that address into an IP number. An A record gives the direct IP, while a CNAME creates an alias that points to another name. Setting them up correctly ensures visitors reach your site without error. Keep the configuration as simple as possible, and remember that any change to hosting may require a DNS update.
If you want a hassle‑free way to keep your domain pointing at a site that is built, hosted and rebuilt for a flat monthly fee, consider a lease model. It handles the DNS work for you while you focus on your business.