DNS propagation describes the period during which recursive resolvers refresh cached answers after a DNS record changes. There is no single global switch: each resolver keeps the old answer until its cache expires.
What controls propagation time?
TTL is the main factor, but browser, operating system, router and ISP caches can also affect what you see. Nameserver changes may take longer because delegation and authoritative DNS data must remain consistent.
How to check DNS propagation
- Query A and AAAA records for website addresses.
- Check MX records before changing email routing.
- Validate NS and SOA records for authoritative DNS health.
- Compare results from multiple geographic locations.
Checker.tr provides worldwide DNS record checks, while DNS Tools Box reports NS, SOA, MX and WWW configuration health.
Test the new server first
When public DNS still points to the old origin, enter the domain and new IP in SkipLink. The preview uses the correct Host header and TLS SNI without changing public DNS or editing a local hosts file.
Avoid common mistakes
Lower TTL before a planned migration, keep the old server online during the transition, verify both apex and www hostnames, and confirm email records before changing nameservers.