Open stitch opened 7 months ago
Weird, so your saying this is rate limiting of the DNS resolving, because there is no MX here? I find this a bit extra weird because it has DNSSEC, since it's not showing it's bogus, it has to have received a signed NSEC(3) response for the non-existence of the MX record, right? (Or is the bogus check limited to a few requests?)
I assume rate limiting or timeouts, these are the only instances i could find with this issue at this moment.
Aalsmeer.nl
Terneuzen.nl
Heerbeeck.nl