yegor
Occasional Visitor
That sounds highly irregular. Can you provide an example of such a behavior? dig/nslookup output and your ASN?My problem with Control D was more than just the raw latency, which the human mind cant really perceive. It was actual pauses in lookups, pages taking 30 seconds to load or just giving up. Each time it happened I would go back to another DNS to test and it was fine. Go back to CD and after some time again lookups would just come to a crawl.
My fiber provider is changing soon so I will have a new opportunity to test out how it works.
There is anti-abuse mitigations in place (as with all public DNS resolvers), but you have to reach hundreds of qps and sustain it for a while before it starts throttling you on free resolvers. Paid ones have higher limits.