DNS (Domain Name System) is the internet's directory that translates domain names into the IP addresses of servers.

DNS is the system that turns a name people can remember, like example.com, into the IP address a computer needs, like 203.0.113.10. Every time you visit a website or send an email, DNS works out where it should go. It's often compared to a phone book for the internet.

DNS links your two key purchases. Your domain is registered at a registrar, and your website lives on a hosting server. DNS is the set of instructions that connects the two, telling the world which server handles your website, which handles your email, and more.

How DNS works

When someone types your domain into a browser, a lookup happens in the background, usually in well under a second:

  1. The browser asks a recursive resolver, normally run by the visitor's internet provider or a service like Cloudflare or Google.
  2. If the resolver doesn't already have the answer cached, it asks a root server, which points it to the servers for the TLD, such as .com.
  3. The TLD servers say which nameservers are in charge of your domain.
  4. Those authoritative nameservers check your domain's zone file and return the answer, such as your server's IP.
  5. The resolver caches that answer for the record's TTL and hands it to the browser, which connects to your server.

Common DNS record types

  • A record: points a name at an IPv4 address. AAAA does the same for IPv6.
  • CNAME: makes one name an alias of another.
  • MX record: says which servers receive email for the domain.
  • TXT: holds text, used for SPF, DKIM, DMARC and domain verification.
  • NS: lists the domain's nameservers.

How DNS points your domain at your hosting

There are two common ways to connect a domain to a host:

  • Change the nameservers at your registrar to your host's nameservers. Your host then manages all your DNS records for you. This is the simplest route for most people.
  • Keep your current DNS and just update the A record (and www) to your host's IP address. This suits you if your email or other services are set up with another DNS provider and you don't want to move them.

Either way, only one set of nameservers is in charge at a time. Editing records anywhere else has no effect.

DNS propagation and common DNS problems

Because resolvers cache answers, a change doesn't appear everywhere instantly. This delay is called propagation. Record changes usually show within minutes to a few hours, depending on the TTL. Nameserver changes can take up to 24 to 48 hours.

Typical issues include:

  • Editing the wrong DNS: the domain uses different nameservers from the ones you changed.
  • Missing records after a move: switching nameservers without copying MX and TXT records breaks email.
  • Typos in IPs or hostnames, and extra or duplicate A records.
  • Expired domains: if the domain lapses, DNS stops resolving.

You can check your records with dig or nslookup, or any online DNS lookup tool. For extra security, DNSSEC signs your records so they can't be forged. AblePage includes free DNS management for every domain you point at us.

DNS questions

How long does a DNS change take?
Usually a few minutes to a few hours for record changes, depending on the TTL. Nameserver changes can take 24 to 48 hours to reach everyone.
Is DNS the same as nameservers?
No. DNS is the whole naming system, while nameservers are the specific servers that hold and answer for your domain's DNS records.
Do I need to move my domain to my web host to use their DNS?
No. You can keep the domain at any registrar and either point its nameservers at your host or update its A record to your host's IP address.
Was this definition helpful?
Share this definition