OnlineHostings.in · Powering Your Digital Growth.
Get Started
Home / Domains / DNS Propagation
DNS PROPAGATION GUIDE

Understand when your DNS changes become visible.

DNS propagation describes how updated DNS information becomes visible through recursive resolvers and cached responses. Learn what to check after changing an A, AAAA, CNAME, MX or TXT record—and why different locations may show different answers for a while.

  • Understand TTL and resolver caching
  • Compare authoritative and recursive DNS answers
  • Follow a practical post-change checklist
AUTHORITATIVE DNSUpdated zone
Resolver AMay have cached answer
Resolver BMay fetch new answer
Resolver CCache expires later
Illustrative DNS lookup flow
WHAT PROPAGATION MEANS

DNS updates are not a single global switch

When you edit a DNS record, the authoritative zone is updated by the DNS provider. Recursive resolvers may continue returning a previously cached response until its cache entry expires or is otherwise refreshed.

01

Authoritative zone

The DNS provider hosting your active zone publishes the current record data. Confirm that you changed the provider serving your domain's delegated nameservers.

02

Resolver cache

Internet service providers, public DNS services and networks may cache answers. Their cached data can expire at different times.

03

Local cache

Your computer, browser, router or operating system may also retain DNS information. A local stale result does not necessarily mean the authoritative record is wrong.

HOW LONG CAN IT TAKE?

TTL matters, but it is not a universal timer

There is no guaranteed time at which every resolver worldwide will show the same result.

Understand TTL

Time to Live (TTL) tells a resolver how long it may cache a DNS response. Once the cached entry expires, the resolver can query again. A previously cached record may remain visible until its remaining cache lifetime ends.

  • A lower TTL set in advance can reduce the expected cache lifetime for subsequent answers.
  • Lowering TTL immediately before a change may not affect records already cached under the previous TTL.
  • Some resolvers and applications may apply additional caching behaviour.
  • Nameserver delegation and DNSSEC changes can involve separate caching and validation considerations.

Example timeline

Change savedAuthoritative provider publishes the new value.
Resolver cache expiresResolvers refresh according to their cached TTL and behaviour.
VerificationQueries from different resolvers are compared for consistency.

Illustrative sequence only—not a promised propagation duration.

HOW TO VERIFY A DNS CHANGE

Check the right record at the right place

Use more than one independent check. A public propagation website or command-line lookup can help compare responses, but neither replaces checking the authoritative DNS configuration.

1. Confirm nameservers

Check the domain's delegated nameservers. If they point to another provider, editing records at the registrar may have no effect on the active zone.

2. Query authoritative DNS

Ask an authoritative nameserver for the exact hostname and record type. This helps establish whether the new value is published in the active zone.

3. Compare recursive resolvers

Check more than one recursive resolver or network. Different answers can indicate cached data, delegation differences or a configuration issue.

4. Test the actual service

For websites, test the hostname and HTTPS response. For email, inspect MX and authentication records and perform a controlled mail test.

LOOKUP METHODS

Useful ways to inspect DNS

These are examples of standard lookup methods. Replace the example hostname with a domain you are authorised to check.

Command line: dig

dig example.com Adig example.com MXdig @1.1.1.1 example.com TXT

Available on many Linux and macOS systems; installation may be required on other platforms.

Windows: nslookup

nslookup example.comnslookup -type=MX example.comnslookup example.com 8.8.8.8

Use Command Prompt or PowerShell to query a DNS server and inspect its response.

Public DNS lookup services

Public DNS providers and independent DNS lookup websites can help compare resolver responses. Check the provider's current documentation and privacy terms before submitting domain information.

This page is an educational guide. It does not submit a live DNS query, scan a domain, or claim that a record has propagated. A live checker would require a configured DNS lookup service.

COMMON REASONS FOR DIFFERENT RESULTS

If a DNS change is not appearing

Wrong DNS provider

The domain may use nameservers hosted somewhere other than the control panel where you made the edit.

Record name mismatch

The record may have been added to the root domain instead of a subdomain, or vice versa. Check the exact hostname being queried.

Conflicting records

Review duplicate, conflicting or invalid records, including CNAME restrictions and MX priorities.

Local or network cache

Compare another network or resolver and clear local DNS cache only when appropriate for your operating system.

Nameserver delegation

A nameserver change may require checking parent-zone delegation and ensuring the new zone contains all required records.

DNSSEC validation

Incorrect DS or DNSKEY configuration can cause validating resolvers to return errors even when records appear present elsewhere.

DNS PROPAGATION FAQ

Frequently asked questions

How long does DNS propagation take?

It depends on cached TTL values, resolver behaviour, the type of change and delegation or DNSSEC factors. Do not rely on a universal fixed time or treat a generic estimate as a guarantee.

Why does my website work for some people but not others?

Different users may query different recursive resolvers or have different cached answers. Also check whether the hostname resolves consistently and whether the web server, virtual host and SSL certificate are configured correctly.

Does flushing my DNS cache speed up global propagation?

No. Flushing a local cache can make your device request a fresh answer, but it does not clear caches held by other resolvers or networks.

Should I lower TTL before changing a record?

For a planned migration, administrators sometimes lower TTL sufficiently in advance, then make the change after allowing existing cached entries to expire. Plan the timing with your DNS provider and service requirements.

Can this page check my domain live?

No. This page explains verification methods but does not run live DNS queries. Use a trusted DNS lookup tool or request assistance from the team.

DNS CHANGE NOT SHOWING?

Get help checking your DNS configuration.

Share the domain, record type, hostname, expected value and the DNS provider. Never send passwords, private keys or account credentials.

Request DNS Assistance