-
Notifications
You must be signed in to change notification settings - Fork 0
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.
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
Add a variety of examples #18
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for writing these. These otherwise LGTM.
@ 300 IN A 192.0.2.1 | ||
AAAA 2001:db8::1 | ||
HTTPS 1 . ech=ABC... | ||
www 300 IN A 192.0.2.1 | ||
AAAA 2001:db8::1 | ||
HTTPS 1 . ech=ABC... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought one of the points of the HTTPS record was that you didn have to keep manually adding A/AAAA sync ups between the apex and www. of a zone ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
HTTPS records allow apex aliasing (as in the next example), but only for clients that support HTTPS records. These examples mostly assume that compatibility with non-HTTPS-record-aware clients is required.
In this case, we could avoid duplicating the A/AAAA records by making www
a CNAME to the apex (as in the multi-CDN example), but I thought that might not be the best choice for our simplest example.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps we just be clear that this retains compatibility (see suggestion above),
Co-authored-by: Erik Nygren <[email protected]>
Fixes #17