On Tue, Oct 17, 2017 at 08:28:02PM +1030, Mal wrote:
> On 17/10/2017 7:14 PM, Viktor Dukhovni wrote:
> 
> > So it seems that the machine in question has the authoritative 
> > server for the zone as its recursive server.  Such mixing of 
> > authoritative and recursive workloads is discouraged these days, 
> > and critically, it breaks DANE in Postfix for any authoritative 
> > zones, because authoritative servers are not validating 
> > resolvers, and don't set the AD bit in authoritative replies.
> 
> Bingo.  That information certainly explains the behavior observed.
> 
> Does this therefore require DNSSEC-validation to be set to "no"
> (for the authoritative NS):
>    dnssec-enable yes;
>    dnssec-validation no;
>    dnssec-lookaside auto;

Um, validation is exclusively done on NON-authoritative lookup 
results.  I'm not sure what you are thinking.  In order:

1. dnssec-enable no; would prevent your BIND server from serving 
required records from a signed zone.  It would prevent ANYONE from 
being able to validate your signed zone.  This is surely not what 
you're seeking?

2. dnssec-validation no; again, this has no effect when you're 
serving authoritative data from a master or slave zone.

3. dnssec-lookaside has been removed!  Disable it now, on any 
nameservers you control.
-- 
  http://rob0.nodns4.us/
  Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:

Reply via email to