Safemode
Regular Contributor
Correct for serve-expired-ttl, i don't find it to be necessary. In my opinion ip-ratelimit is too agressive at this given time so i leave it at default.Thanks, is ratelimit and ip-ratelimit basically the same? Also, I noticed your not using serve-expired-ttl, correct.
Code:
ratelimit: <number or 0>
Enable ratelimiting of queries sent to nameserver for performing
recursion. If 0, the default, it is disabled. This option is
experimental at this time. The ratelimit is in queries per second
that are allowed. More queries are turned away with an error
(servfail). This stops recursive floods, eg. random query names,
but not spoofed reflection floods. Cached responses are not rate-
limited 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, 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.
ip-ratelimit: <number or 0>
Enable global ratelimiting of queries accepted per ip address. If
0, the default, it is disabled. This option is experimental at
this time. The ratelimit is in queries per second that are
allowed. More queries are completely dropped and will not receive
a reply, SERVFAIL or otherwise. IP ratelimiting happens before
looking in the cache. This may be useful for mitigating amplifica-
tion attacks.