• 3 Posts
  • 418 Comments
Joined 3 years ago
cake
Cake day: June 9th, 2023

help-circle







  • I was a subscriber to Consumer Reports for years and trusted them implicitly because they seemed so thorough and rigorous. Then they did reviews on a subject with which I am intimately familiar (it was computer related), and I was shocked at how badly they fumbled just about everything. I’ve also seen some really dubious ratings on high ticket items like cars that I knew were not great, so I take their ratings with grain of salt anymore.

    The fact that Whirlpool is even on this list makes it a joke to me. I will say I’ve had a Miele dishwasher in the past and it was fucking awesome, and have heard great things about a lot of Bosch appliances. But LG and Whirlpool frequently put out trash appliances.


  • There are lots of reasons to use really low TTLs, but most are a temporary need. Most of the times I had to set low TTLs for records were for hardware migration projects where services were getting new IP addresses. But in a well managed shop this should always be temporary. The TTL would be set low the day before the change, then set back to a normal value the day after the change. I feel the author is correct in that permanently setting low TTLs just covers up a lack of proper planning and change management.

    The only thing off the top of my head that I can think absolutely requires a permanently low TTL is DNS based global load balancing for high uptime applications. But I’m sure there are other uses. I agree that the vast majority of things do not need a low TTL on their DNS record.