3 ms·
> Mitigating this could be as blunt as setting DNS TTLs to 5 minutes, then putting "sleep 300" at the start of each server's shutdown script. When you decide to
by toast0 7y ago
> Mitigating this could be as blunt as setting DNS TTLs to 5 minutes, then putting "sleep 300" at the start of each server's shutdown script. When you decide to kill a server, first kill its DNS record so that nothing refers to it anymore, then start the waiting period before actually removing it from rotation.
If I had a dollar for everytime traffic stopped to an IP after the DNS ttl expired, I wouldn't have any dollars. After taking IPs out of DNS for www.popular site, I would continue to see traffic for weeks, and the TTL was set for somewhere like 5 minutes, an hour tops. Edit: also, when we moved our authoritative DNS, the old provider kept seeing queries for at least 6 weeks.
If the only thing preventing you from sending private data or receiving trusted data is that it came from an IP you got from DNS, it's not secure.
- mjw1007 7y agoI think what matters is whether the certificate authorities honour TTL correctly when they do domain-control validation. If they do, then the procedure above (and doing everything over https) should be enough, I think.
- kstrauser 7y agoOh, buddy, you know that's right. There are plenty of IPSs like, "5 minutes, lol! Two weeks it is!" What I proposed was a blunt force tool to try to help mitigate the problem, but you're 100% correct that it's not sufficient. Key pinning would go a lot further towards fixing it. What I suggest could be rolled out pretty quickly and without risk, though, so IMHO it's worth adding to the to-do list.