24/7 technical support
24 public DNS servers and the domain's authoritative servers

DNS propagation check

Have your domain's DNS records reached DNS servers in different parts of the world? After a name server, IP or MX change, you can see here which servers have updated the record.

If you enter an IP address, its reverse DNS (PTR) record is looked up.

How it works

Why does DNS propagation take time?

When you change a DNS record, the new value first appears on the domain's authoritative name servers. Servers run by internet service providers and public DNS services, however, keep the old answer in their cache until the record's TTL expires.

Authoritative servers

These are the servers listed in your domain's NS records. They hold the correct value of the record, and the tool compares the other servers against this answer.

Public DNS servers

Resolvers used by visitors, such as Türk Telekom, Google, Cloudflare and Quad9. If you see an old answer, their cache has not yet been refreshed.

TTL

Specifies in seconds how long the record is kept in cache. Lowering the TTL to 300 seconds before a migration speeds up the switchover.

A record changes usually propagate within a few minutes to a few hours. For a name server (NS) change, this can take up to 24–48 hours depending on the extension.

Record types

Which record should I check?

TypeWhat it doesWhen to check it
APoints the domain to an IPv4 address.When you move your site to new hosting or a new server
AAAAPoints the domain to an IPv6 address.If your server uses IPv6
CNAMELinks one name to another (e.g. www → main domain).When connecting a subdomain, CDN or online store platform
MXSpecifies which server receives email sent to your domain.When you move business email to another service
NSShows which name servers manage the domain's DNS.When you point the domain to another company or to Cloudflare
TXTSPF, DKIM, DMARC and verification records for services such as Google and Microsoft.If email lands in spam or a service asks for domain verification
CAARestricts which certificate authorities can issue SSL for your domain.If an SSL certificate cannot be issued
SOAThe zone's primary server, serial number and timing settings.To see whether a change has reached the authoritative servers (serial number)
SRVSpecifies which server and port a service (e.g. _sip._tls, Minecraft) runs on.When setting up a game server, VoIP or Microsoft 365
PTRMaps an IP address back to a name (reverse DNS).If you send email from your own server
Questions

Frequently asked questions about DNS propagation

Some servers show a different IP. Is something wrong?
Not always. If you have just changed the record, those servers keep showing the old value until the TTL expires; you only need to wait. Large sites also return different IPs depending on the visitor's location because of CDNs and load balancing. In that case, a "Different" result does not indicate an error.
The old site still opens on my own computer. What should I do?
Your computer and modem also cache DNS answers. On Windows, run the ipconfig /flushdns command in the command prompt and restart your browser. If the problem persists, try restarting your modem or waiting a few hours.
The authoritative servers row shows "No response".
This means the name servers listed in the domain's NS records are not answering queries. Check that the name server names are spelled correctly and that the DNS zone has been created on those servers. If your domain is with Kilitkutu, you can write to our support team.
Are my lookups recorded?
No. The name you look up is passed to DNS servers through our server; your IP address is not sent to these servers, and lookups are not stored. To prevent abuse, the same visitor can make a maximum of 30 lookups in 5 minutes.

Would you rather not deal with DNS settings?

Move your domain and hosting to Kilitkutu, and we will set up your DNS, email and SSL records for you.