New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Catalog Zone Changes #64

Open

ShaneMcC opened this issue Apr 15, 2019 · 0 comments

Member

ShaneMcC commented Apr 15, 2019

Our current catalog zone is based on what bind 9.11 implemented.

Bind 9.15 (and subsequently, 9.16) will likely update their implementation based on the latest version of the drafts, so we should make sure we generate valid zones (https://datatracker.ietf.org/doc/draft-muks-dnsop-dns-catalog-zones/).

Some things of note:

The SHA1-of-wire-format is not strictly required, and can be any unique per-zone string. (We may want to for example use our internal domain-id to make the zones nicer to read
We currently define the allow-transfer record as a single APL, but this should be separate as per https://tools.ietf.org/id/draft-muks-dnsop-dns-catalog-zones-04.html#sec-network

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment