A registrar is the company that you buy your domain name from. Domains usually cost around $10-20 per year, though it depends on the suffix and how much the registrar chooses to charge.
Once a domain is purchased with a particular registrar, it can be transferred to a new registrar if desired. In order to prevent fraud, however, changing registrars is a cumbersome process involving email approvals, transfer codes, paying the new registrar, etc — so it can be rather logistically inconvenient to do.
Getting registrar credentials gives us the power to change a domain’s name servers.
The Name Servers for a domain are the computers in charge of knowing (and telling other computers on the Internet) how that domain works, i.e. what computers on the Internet host the domain’s website, what computers on the Internet receive email sent to that domain, and what computers on the Internet are allowed to send email from that domain.
Domains always have at least two nameservers specified and sometimes several more (this is to help ensure that if one fails there’s another one to contact for the answers).
Name Servers store this information in what are called DNS records. For this reason, the company providing the Name Servers is known as a domain’s “DNS Provider.”
Getting credentials to the DNS provider allows us to change a domain’s DNS records. Here’s how to add us.
A domain’s DNS records are the things that specifically tell the rest of the Internet how to treat that domain, such as where to route email messages intended for that domain and where to send requests for that domain’s website. Each record is like a row in a spreadsheet; the main columns are “type”, “name” and “value”
There are four main types of DNS records (and several less common ones):
- A records
These link a domain name, including specific prefixes like “www.domain.com” or “intranet.domain.com”, to an IP address — that is, a specific device connected to the Internet somewhere.
- CNAME records
These are like aliases, specifying that a certain domain name or prefix should actually send traffic to whatever the DNS record is of some other domain, e.g. calendar.cornershopcreative.com has a CNAME record of ghs.google.com
- MX records
These link a domain to the names of servers that handle the domain’s email. Often multiple MX records exist so that if one mail server is having problems emails can be routed to another server without disruption.
- TXT records
These are used for a variety of purposes, such as authorizing specific computers to send email on that domain’s behalf (called SPF)
DNS records are what specify what computer a website lives on, which means they specify a domain’s website host.
The host is the provider of the computing infrastructure that powers the website.
Every website must be “hosted” on at least one computer (often called a server) – the machine in charge of sending the data for the website to a site visitor’s device. While sometimes we use the word “host” to refer to the specific computer the website lives on, more commonly the word “host” refers to the company that owns and maintains that computer and its connection to the internet (as well as likely thousands of other such computers!).
Different hosts use different computers and different technologies to provide the computing resources necessary to power a website. Some hosts use really powerful computers, give those computers really good internet connections, and put very few websites on each computer; others don’t. (And sometimes the “computer” hosting a website isn’t actually a single computer at all, but a complicated system of stuff that all together functions like one computer.)
Some hosting companies do a good job and others don’t. But since every host is free to do things a little differently — sort of like how everyone’s phone has a unique combination of wallpaper, apps, and so on — it can be challenging to know how to best work with even just the hosts that are good. For that reason, we focus on Kinsta and Pantheon so at least we can have deep familiarity with a few good hosts. This is not to say these are the only good hosts in the world, but they’re the ones we know are good and have learned our way around the best.
It’s very common for one company to provide all three of these separate services — domain registration, name servers, and hosting — as it can be convenient and simple (especially for non-techies) to not have to worry about keeping this stuff in order across different vendors. But they are, in fact, distinct services and don’t need to be done by the same company.
In fact, there are many companies that specialize in just one of these things. Kinsta, for example, just hosts websites — though they partner with Amazon to host DNS records through Amazon’s name servers if needed. As another example, Cloudflare just provides name servers to manage DNS records (because they do fancy stuff with those DNS records to allow them to provide caching and security). So sometimes figuring out what credentials you need to make a particular change can be confusing.
Often when a DNS record is changed from pointing at one to host to pointing to another, it can take a while before everyone sees the new website, and not everyone starts seeing the new website at the same time. This is due to DNS propagation, the phenomenon of spreading a DNS record throughout the Internet.
Imagine that any time you wanted to visit Google.com, your device had to lookup google.com’s name servers to find where the DNS records were stored, then go check the values of those DNS records to figure out what computers were actually hosting the google.com website. That would stink for two reasons: First, it’d be annoying and slow for YOU, because all of that would have to happen every single time you wanted to visit google.com. Second, it’d be terrible for the poor name servers, because billions of people would constantly be asking them the same damn question over and over and the name servers would likely get overwhelmed.
Fortunately, the answer to the question “what computers serve the website for google.com” doesn’t change very often, so to save time lots of computers and devices throughout the internet just remember the answer – which is to say, they can keep their own copy of the DNS records for google.com on hand. So instead of your device having to ask one of those original (called “authoritative”) name servers where google.com lives, your device may just remember the answer itself for a little while — and if it’s forgotten, it may just go ask a device more nearby on the internet (like your internet provider’s DNS servers).
Because all these devices all over the place are storing copies of the original DNS records, when changes to the original DNS records are made, it can take a while for those changes to take effect — the copies of those DNS records need to be “refreshed” with the latest information from the authoritative servers. And though DNS records can provide guidance on how long those cached copies of themselves should be kept before they expire and the original DNS records are re-checked (called “time to live”), it’s not an exact science.