> -Original Message-
> From: Mark Andrews [mailto:ma...@isc.org]
>
> Named does not check that a parent zone has NS records for a child
> zone on the same server. Always add delegating NS records.
>
> As for ENT returning NXDOMAIN. Early versions of the specifications
> of DNSSEC said the
Named does not check that a parent zone has NS records for a child
zone on the same server. Always add delegating NS records.
As for ENT returning NXDOMAIN. Early versions of the specifications
of DNSSEC said there were no NAMES, rather than NAMES with RECORDS,
between names in a DNSSEC sorted
> -Original Message-
> From: Woodworth, John R
> -Original Message-
> From: bind-users [mailto:bind-users-boun...@lists.isc.org] On Behalf Of Phil
> Mayers
> >
> > On 12/02/2017 11:09, Woodworth, John R wrote:
> >
> > > SAMPLE ZONES:
> > > 101{redacted}.com. (REAL ZON
-Original Message-
From: bind-users [mailto:bind-users-boun...@lists.isc.org] On Behalf Of Phil
Mayers
>
> On 12/02/2017 11:09, Woodworth, John R wrote:
>
> > SAMPLE ZONES:
> > 101{redacted}.com. (REAL ZONE FILE)
> > jwjw.sales.101{redacted}.com. (REAL ZONE FILE)
>
> You ar
On 12/02/2017 11:09, Woodworth, John R wrote:
SAMPLE ZONES:
101{redacted}.com. (REAL ZONE FILE)
jwjw.sales.101{redacted}.com. (REAL ZONE FILE)
You are missing the glue NS records in the parent zone (just verified by
local test of the before/after case). You need:
jwjw.sales.1
All,
I am asking for advice/ comments/ best-practices for bind
configuration and zone RRs to avoid potential issues with
Empty Non-Terminal (ENT) domain names.
Before continuing, I feel I must point out I am a big fan
of improvements in network and protocol efficiency
including RFC-8020. I also f
6 matches
Mail list logo
