Skip to content
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

Merged
merged 3 commits into from
Oct 21, 2024
Merged

Add a variety of examples #18

merged 3 commits into from
Oct 21, 2024

Conversation

bemasc
Copy link
Collaborator

@bemasc bemasc commented Oct 11, 2024

Fixes #17

Copy link
Collaborator

@enygren enygren left a 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.

@bemasc bemasc requested a review from enygren October 14, 2024 12:58
Comment on lines +97 to +102
@ 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...

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 ?

Copy link
Collaborator Author

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.

Copy link
Collaborator

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),

@seanturner
Copy link

@bemasc @enygren merge when ready; see email.

@enygren enygren merged commit 013a39e into main Oct 21, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add some examples (and perhaps operational considerations) especially for the Multi-CDN case
5 participants