Open wttw opened 9 months ago
The initial reverse DNS lookup with an empty cache can take 5 seconds or more, and the resolver seems to be refused by the in-addr.arpa authoritative servers.
We're using unbound as a resolver, with a max TTL override of 60 seconds (same as emailstuff.org uses). That probably means we're fetching the whole resolution tree with an empty cache once a minute, which may be hitting throttles near the root?
Short term mitigation, remove the max ttl override. Longer term, sniff some traffic and see what's happening. Maybe implement a custom resolver?
During the processing phase the spinner sits on Basics for a long time.