Turkey (Turkish)
Germany (German)
Worldwide (English)
Device cache
Your operating system can temporarily store previously resolved domain and IP mappings.
Halkali merkez neighborhood fatih st ozgur apt no 46 , Kucukcekmece , Istanbul , 34303 , TR
If a domain still opens the old server, works on one device but not another, or becomes inaccessible after a DNS change, the cause is usually a stale record stored at one of the DNS caching layers.
A DNS response may be cached by several systems before the request reaches the authoritative nameserver. Clearing only one layer may not be enough.
Your operating system can temporarily store previously resolved domain and IP mappings.
The browser can reuse existing connections, service workers and internal network state.
A modem, router or company network can use its own recursive resolver and cache.
Your ISP or public DNS service can retain the previous response until the record TTL expires.
Run the command for your operating system, close the browser completely and test again. Administrator privileges may be required.
ipconfig /flushdns
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
sudo resolvectl flush-caches
sudo systemctl restart systemd-resolved
sudo systemctl restart NetworkManager
If the operating system command does not solve the issue, test the remaining caching layers in order.
A private window helps test without most existing cookies and local browser state.
End all browser processes and reopen it so existing connections are not reused.
Power off the modem or router briefly if it maintains a local DNS cache.
Compare Wi-Fi with mobile data to determine whether the problem is local or provider-based.
Temporarily test a reputable public resolver to compare recursive DNS responses.
VPN, antivirus, proxy and filtering software can use separate DNS settings.
Use these commands to compare your normal resolver with an authoritative or public DNS response.
Resolve-DnsName example.com
Resolve-DnsName example.com -Server 1.1.1.1
nslookup example.com
nslookup example.com 8.8.8.8
dig example.com
dig @1.1.1.1 example.com
Each DNS record has a TTL value. Recursive resolvers may continue returning the previous value until that cached response expires. Different networks can therefore update at different times.
The DNS provider publishes the new A, AAAA, CNAME or nameserver record.
Resolvers that already cached the previous answer may retain it until the TTL period ends.
Each recursive DNS provider requests the updated answer when its cached record expires.
The browser, operating system and local network must stop reusing the previous connection or address.
For a temporary test on your own computer, you can map a domain to a specific IP address. Remove the entry after testing because it overrides normal DNS resolution.
203.0.113.10 example.com www.example.com
Only use an IP address you trust. An incorrect hosts entry can redirect the domain to the wrong server and will continue working even after DNS records change.
Important points to check before changing DNS records again.
No. It clears only the cache on your own device. Other networks and recursive DNS providers refresh their records according to their cached TTL values.
The two connections usually use different recursive DNS resolvers. One resolver may have refreshed the record while the other still returns the previous IP address.
The root domain and www hostname can use different DNS record types and TTL values. Check both records separately.
Not immediately. First compare authoritative records, recursive resolver results and TTL values. Repeated changes can make troubleshooting harder.
Yes. If the domain is still directed to the old server, that server can return a different or expired certificate. Verify the returned IP address before changing the certificate.
The effective time depends on the previous TTL, registry processing when nameservers change, recursive resolver behavior and local caches. Check actual DNS responses instead of relying on one fixed waiting period.
Use the DNS preview tool to test the destination server without waiting for local cache refresh, or contact our team for technical guidance.