Skip to content
Host4u Limited

How DNS works (records and propagation)

Support Portal  »  Knowledgebase  »  Viewing Article
There was a problem loading the comments.
  Print
  • 13/11/2026 9:38 am

DNS, the Domain Name System, is the internet's address book. It turns a name people can remember, such as example.com, into the address of the server that holds the website or receives the email.

The parts

  • A domain name is the name you register.
  • DNS records are the entries that say where things for that name are: one for the website, another for email, and so on. See A, CNAME, MX, TXT and PTR records explained.
  • A DNS zone is the set of records for one domain.
  • Nameservers are the servers that hold your zone and answer questions about it. Your domain's nameserver setting says which servers those are. See Pointing your domain at your hosting.

What happens when someone visits your website

  1. Their device asks its internet provider's DNS server for the address of your domain.
  2. That server asks the domain's nameservers.
  3. The nameservers answer with the record, for example the address of your web server.
  4. The device connects to that address.

Why changes take time ("propagation")

DNS answers are remembered (cached) by providers so they do not have to ask again. Each record has a TTL (time to live), the number of seconds an answer may be remembered. The records in cPanel's zone editor use 14,400 seconds (4 hours) by default. So after a change, some people see the new answer straight away and others see the old one until their provider's copy expires. Nameserver changes can take up to 24 hours to reach everyone.

To make a change faster, lower the TTL a day before you make it.

Checking your DNS records

To see what a domain's records are right now:

  • A DNS checker website such as intoDNS: enter your domain and it lists the nameservers and records the world sees.
  • On your computer, from a terminal or Command Prompt:

bash nslookup -type=A example.com nslookup -type=MX example.com nslookup -type=NS example.com

Replace example.com with your domain. Use A for the website address, MX for email and NS for the nameservers.

If the result is not what you expect, the change may still be spreading (see above), or you may be editing the records somewhere that is not where your nameservers point.

Where to change things


Share via
Did you find this article useful?  

Related Articles


Self-Hosted Help Desk Software by SupportPal