> On 2 Jul 2020, at 11:18, John Levine wrote:
>
> In article <9056955.dJ39pTEj9z@linux-9daj> you write:
>> On Wednesday, 1 July 2020 09:41:49 UTC Jan Včelák wrote:
>>> We just opened this discussion internally at NS1 because we serve some
>>> zones with more than 10 NS records where each NS req
In article <9056955.dJ39pTEj9z@linux-9daj> you write:
>On Wednesday, 1 July 2020 09:41:49 UTC Jan Včelák wrote:
>> We just opened this discussion internally at NS1 because we serve some
>> zones with more than 10 NS records where each NS requires glue and our
>> proprietary server by design adds gl
> > I also think there is another proprietary implementation of an
> > authoritative server in the wild which implements similar policy. It
> > picks a small random subset of the NS records and adds A/ just for
> > these names. If the QNAME matches a name in the NS, A/ for that NS
> > is al
On Wednesday, 1 July 2020 09:41:49 UTC Jan Včelák wrote:
> ...
>
> We just opened this discussion internally at NS1 because we serve some
> zones with more than 10 NS records where each NS requires glue and our
> proprietary server by design adds glue only for the first four NS
> records. We are d
Tim Wicinski has requested publication of draft-ietf-dnsop-dns-zone-digest-08
as Proposed Standard on behalf of the DNSOP working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-dnsop-dns-zone-digest/
___
DNSO
> Abstract:
>The DNS uses glue records to allow iterative clients to find the
>addresses of nameservers that live within the delegated zone. Glue
>records are expected to be returned as part of a referral and if they
>cannot be fitted into the UDP response, TC=1 MUST be set to info