- documentation proposes ratelimit of 1000 (closer to what upstream

  servers expect from us).

git-svn-id: file:///svn/unbound/trunk@3427 be551aaa-1e26-0410-a405-d3ace91eadb9

diff --git a/doc/Changelog b/doc/Changelog
index 55637959704925c34ad5ebb1857e2c66031e72e2..5bfb821e094bdca73d12ba7c297e7062b1c5335a 100644 (file)
--- a/doc/Changelog
+++ b/doc/Changelog
@@ -1,5 +1,7 @@
 21 May 2015: Wouter
        - iana portlist update.
+       - documentation proposes ratelimit of 1000 (closer to what upstream
+         servers expect from us).
 
 20 May 2015: Wouter
        - DLV is going to be decommissioned.  Advice to stop using it, and

diff --git a/doc/example.conf.in b/doc/example.conf.in
index 6c54ef2c62910fdf3235e7861c6995e9f71274ad..277d8f4763456686610d3a85ea71eb2a308812bf 100644 (file)
--- a/doc/example.conf.in
+++ b/doc/example.conf.in
@@ -571,10 +571,10 @@ server:
 
        # override the ratelimit for a specific domain name.
        # give this setting multiple times to have multiple overrides.
-       # ratelimit-for-domain: example.com 100
+       # ratelimit-for-domain: example.com 1000
        # override the ratelimits for all domains below a domain name
        # can give this multiple times, the name closest to the zone is used.
-       # ratelimit-below-domain: example 100
+       # ratelimit-below-domain: example 1000
 
 # Python config section. To enable:
 # o use --with-pythonmodule to configure before compiling.

diff --git a/doc/unbound.conf.5.in b/doc/unbound.conf.5.in
index 10939b60af18f1b0eb871b3089ae89ab3dc3033c..650c3651e2f80f9cc48a5bc532493295f8799bac 100644 (file)
--- a/doc/unbound.conf.5.in
+++ b/doc/unbound.conf.5.in
@@ -1002,7 +1002,7 @@ turned away with an error (servfail).  This stops recursive floods, eg. random
 query names, but not spoofed reflection floods.  Cached responses are not
 ratelimited by this setting.  The zone of the query is determined by examining
 the nameservers for it, the zone name is used to keep track of the rate.
-For example, 100 may be a suitable value to stop the server from being
+For example, 1000 may be a suitable value to stop the server from being
 overloaded with random names, and keeps unbound from sending traffic to the
 nameservers for those zones.
 .TP 5