public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 3/3] Unbound: Use aggressive NSEC
Date: Thu, 23 Aug 2018 14:43:34 +0100	[thread overview]
Message-ID: <b1c83bd3fff61b4949fa8554a2858178876d29a9.camel@ipfire.org> (raw)
In-Reply-To: <4c59f5c0-751f-c74c-1f3a-5a8dd27cfe9f@link38.eu>

[-- Attachment #1: Type: text/plain, Size: 966 bytes --]

Not sure if this actually makes a difference in reality. It is quite
unlikely to hit a match here.

But I can live with this change.

-Michael

On Sun, 2018-08-19 at 20:13 +0200, Peter Müller wrote:
> This avoids some needless lookups to destination domains
> with a very high NXDOMAIN rate and reduces load on upstream
> servers.
> 
> See https://nlnetlabs.nl/documentation/unbound/unbound.conf/
> for further details.
> 
> Signed-off-by: Peter Müller <peter.mueller(a)link38.eu>
> ---
>  config/unbound/unbound.conf | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/config/unbound/unbound.conf b/config/unbound/unbound.conf
> index 8b5d34ee3..8ad6bcb03 100644
> --- a/config/unbound/unbound.conf
> +++ b/config/unbound/unbound.conf
> @@ -60,6 +60,7 @@ server:
>  	harden-referral-path: yes
>  	harden-algo-downgrade: no
>  	use-caps-for-id: yes
> +	aggressive-nsec: yes
>  
>  	# Harden against DNS cache poisoning
>  	unwanted-reply-threshold: 5000000


  reply	other threads:[~2018-08-23 13:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-19 18:13 Peter Müller
2018-08-23 13:43 ` Michael Tremer [this message]
2018-08-27 15:26 ` [PATCH 3/3 v2] " Peter Müller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b1c83bd3fff61b4949fa8554a2858178876d29a9.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox