All questions
Q & A DNS Records · September 11, 2026

Why does dig show a different answer than my browser?

Almost always: your operating system or browser has its own DNS cache separate from the resolver you told dig to query. dig queries the resolver directly, bypassing local caches. To match: flush your OS DNS cache (macOS: sudo dscacheutil -flushcache, Windows: ipconfig /flushdns, Linux: systemd-resolve —flush-caches or restart nscd), then check again in the browser.

Read the full guide
How DNS Propagation Actually Works (And Why 24 Hours Is a Lie)
DNS propagation isn't magical. It's a function of TTLs, resolver caches, and how you sequenced your DNS change. Understand the moving parts and you can plan changes with confidence — and know when '24 hours' is nonsense.
Related questions
Can I force DNS propagation to be faster? Does Cloudflare's proxy affect DNS propagation? How do I check DNS propagation globally? Why does DNS propagation take 24 hours?