3 ms·
Correct me if I am wrong, but a TTL is specific to nameservers. So if you switch from easyDNS to say cloudflare your TTLs get completely reset and the caching d
by dubcanada 7y ago
Correct me if I am wrong, but a TTL is specific to nameservers. So if you switch from easyDNS to say cloudflare your TTLs get completely reset and the caching does as well.
- FDSGSG 7y agoFirstly, in practice this would be very unlikely to affect a domain for an extended period of time, none of the big providers really treat TTLs like that. It's the mere spirit of the thing that counts. However, I don't see why changing your nameservers would help if your resolver was always hitting a cache entry with a 1yr TTL.
- toast0 7y agoIn theory, maybe? But if the TTL is 1 year, why would my caching resolver try to find the new nameservers? Also, there's a long tail of totally garbage behavior in the DNS space. At my last job, as part of moving our domains off of Dyn/Oracle, we delegated the domains to our self hosting via the domain registry, and changed the NS records at Dyn to point only at our self hosting, but we were still seeing a steady trickle of traffic to Dyn after 30 days.
- blackflame7000 7y agoIt would change the Authoritative server's TTL but it wouldn't necessarily propagate to caching DNS servers.