On 05/26/2015 05:31 PM, Mark Andrews wrote:
Well 208.67.220.220 returns the wrong SOA record which is why you
are getting the message. For that matter why are you talking to
208.67.220.220 in the first place? It is not normally involved in
resolving dns2.registrar-servers.com.
Mark,
Thank
On 26/05/15 22:00, Mike Hoskins (michoski) wrote:
However, as we've mostly just been turning knobs in an attempt to minimize
log entries... insight from operators is appreciated.
We run with:
rate-limit { responses-per-second 20; };
3x internet-facing resolvers answering about 5-25k qps a
Hi Mike,
In production since July 2013 without complaints and believe it has
helped here.
rate-limit { responses-per-second 10; window 5; };
best!
jim
On 5/26/2015 5:00 PM, Mike Hoskins (michoski) wrote:
Hi folks,
I've read about RRL with interest since its inception, but just now
g
On Wed, 27 May 2015 07:50:12 +0100,
Lucio Crusca wrote:
>
> I've now fixed the MNAME and I have to wait propagation before testing
> again, but I'm really confident it will solve the problem,
Fammi sapere, per piacere ...
Niall
___
Please visit h
4 matches
Mail list logo