1. Overview
  2. The basics
  3. Nameservers
  4. Records
  5. Waiting
  6. Troubleshooting
  7. Checking
  8. Questions
  9. More questions
  10. Next
Guide

How DNS and nameservers actually work.

DNS is the system that turns a domain name into the address of a server. Nameservers are where your domain's records are kept.

Wooden signpost with three arrows under a lantern at dusk
The basics

A phone book for the internet.

Computers find each other by numeric addresses, but people use names. The Domain Name System, DNS, translates one into the other. When someone types your domain into a browser, a lookup asks where that name lives and receives an answer. Only then does the browser connect to the web server and request your page.

Radio tower on a forested ridge at dusk
Nameservers

Who answers for your domain.

Every domain has nameservers assigned to it. They hold the DNS records and answer the lookups. You set a domain's nameservers at the company where you registered it. If you want your hosting provider to manage the records, you point the domain at the provider's nameservers. With Farrington Hosting those are ns1.farringtonhosting.com and ns2.farringtonhosting.com. The steps are on point your domain.

Glowing glass panel above dark server equipment
Records

What the records say.

An A record connects a name to an IPv4 address. A CNAME makes one name an alias of another. An MX record says which server receives email for the domain. A TXT record holds text used for purposes such as verification. Together they route your website, your subdomains, and your mail. In cPanel, a DNS zone editor lets you view and change them.

Control panel with sliders, dials and buttons
Waiting

Why changes take time.

DNS answers are cached by many servers along the way, each for a set period called the time to live, or TTL. After you change nameservers or a record, some places keep the old answer until their cache expires. This spreading of the change is called propagation. It often finishes in minutes to a few hours, and can take up to 48 hours. During this period, different people may briefly see different results. This also affects when an SSL certificate can be issued, and where email goes.

Misty forested mountains at dusk
Troubleshooting

Common record mistakes.

Typical mistakes are a missing www record, an MX record still pointing at the old mail provider, and a stray extra A record that sends some visitors to the wrong server. When a site or mail misbehaves after a change, compare your records with what you expect. Fix one record at a time, then allow time for caches to expire before testing again.

Headset on a dark desk beside server equipment
Checking

How to check your work.

Look up your domain's nameservers with a public lookup tool, then check the A, MX, and TXT records separately. Test from a different network, such as a phone off Wi-Fi, to avoid your own cache. If results differ by location, propagation is probably still in progress. Note the time you made the change so you can judge how long it has been.

FAQ (1 of 2)

Common questions.

What is the difference between a registrar and a host?

A registrar is where you register and renew the domain name. A host is where your website and email are stored. They can be different companies.

Which DNS record decides where my email goes?

The MX record. It names the server that receives mail for your domain, so set up mailboxes and records on the new host before you switch.

Can I check my DNS records?

Yes. Public DNS lookup tools show your domain's nameservers and records. Remember that they can show cached answers.

FAQ (2 of 2)

More questions.

Why does my site work for me but not for someone else?

Different networks may still hold old cached answers. Waiting for propagation usually resolves it.

Next step

Questions about DNS? Call (828) 770-9428.