News for hackers. Stuff that matters.
Re:Problems with low DNS TTLs by rebelde on Monday March 29, 2021 @11:03AM (#26622769)
Windows Update. To reboot a server, you need to take it out of production. With a TTL of 5 minutes, it can take an hour for (nearly) all users to stop using that server.
Re:Problems with low DNS TTLs by yjftsjthsd-h on Monday March 29, 2021 @11:27AM (#26623174)
Sorry - why would a 5m TTL take an hour to stop using? Shouldn't it be 5 minutes?
Re:Problems with low DNS TTLs by Twirrim on Monday March 29, 2021 @11:54AM (#26623702)
If things behaved nicely, yes. There's all sorts of weird DNS caching behaviour out there. It's not unusual to find folks with DNS servers / clients that are caching records for 1 hour+, and then of course there's people running super old versions of Java that used to cache DNS forever by default (before JDK 6). There's a very clear set of user that seem to cache for 10-15 minutes, regardless of any DNS TTL.
Re:Problems with low DNS TTLs by marcosdumay on Monday March 29, 2021 @01:38PM (#26625405)
You can't fix systems that ignore your TTL by specifying lower TTL values.
Re:Problems with low DNS TTLs by Twirrim on Monday March 29, 2021 @02:10PM (#26625894)
Sure. My general approach is to use lower TTL values (~ 5 minutes) and just accept that if people do dumb things, they just have to put up with things randomly breaking unexpected.
Re:Problems with low DNS TTLs by EricE on Monday March 29, 2021 @01:43PM (#26625467)
Good grief- you do not need to reboot the server; just flush the cache https://www.dnsstuff.com/clear-flush-dns-server-cache-window...
Re:Problems with low DNS TTLs by majewsky on Monday March 29, 2021 @04:05PM (#26627488)
They mean they're rebooting the server having the IP that's entered in DNS, not rebooting the client consuming that service.