2 ms·
Is this specifically an issue with the Facebook app? Or is it just a predicable consequence of DNS responses no longer being cached due to query failures for a
by Ajedi32 5y ago
Is this specifically an issue with the Facebook app? Or is it just a predicable consequence of DNS responses no longer being cached due to query failures for a site as popular as Facebook?
- treesknees 5y agoIt is certainly not specific to Facebook, but the scale at which Facebook is referenced across websites and apps is pretty unique (I can only think of a few key players like Google who would cause a similar load.) And to clarify a bit, the queries aren't "no longer being cached due to query failures", it's because their TTL expires and the resulting SERVFAIL from the next query (which fails) isn't cached at all.