News for hackers. Stuff that matters.

A comment on EasyDNS threatened with criminal complaint if client data not disclosed. Parent comment

Re:EasyDNS threatened with criminal complaint if client data... by dubcanada on Monday September 16, 2019 @02:23PM (#20987047)
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.
[ Parent | on HN ]
Re:EasyDNS threatened with criminal complaint if client data... by toast0 on Monday September 16, 2019 @02:52PM (#20987307)
In 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.

[ Parent | on HN ]
Re:EasyDNS threatened with criminal complaint if client data... by FDSGSG on Monday September 16, 2019 @02:28PM (#20987099)
Firstly, 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.

[ Parent | on HN ]
Re:EasyDNS threatened with criminal complaint if client data... by blackflame7000 on Monday September 16, 2019 @04:11PM (#20988093)
It would change the Authoritative server's TTL but it wouldn't necessarily propagate to caching DNS servers.
[ Parent | on HN ]