[makiniq0z]

Instead of running local resolvers for caching, they should have used nscd DNS cache to decrease the volume of queries from those machines running the logs tasks. nscd is not designed for that, but is long known to have this best-use practice: https://prefetch.net/blog/2011/03/27/configuring-nscd-to-cac...

[ahoka]

Doesn’t systemd-resolved do this by default now, so this is a non-issue?

[placatedmayhem]

Yes. Also, nscd is irrelevant in at least a few ecosystems. Java and (I think) Go try to do their own resolving instead of using libc. Java's resolver, in particular, is braindead in the default configuration: infinite record caching, ignoring TTLs.

systemd-resolved solves this, as does running unbound or similar as a local cache.

[factormeta]

Yeah but then they not going to have a fancy blog about how they hit the AWS traffic limit to VPC resolver! Now days a tech blog like this is gonna be good tech PR for the company.

[bux93]

This kind of blog is mainly to give potential hires an insight into the day-to-day goings on of their prospective employer.

This blog doesn't make any sense whatsoever, encouraging people with low skills to apply.

[emushack]

That's... quite the interpretation. Do you really think that Stripe's intention is to "encourage people with low skills to apply" by writing a blog post about monitoring DNS?