This moves the informative guidance text for alternative setups to an appendix. The reason for this is that this text is not required for the ANAME protocol but provides useful information for providers that use a non-traditional DNS architecture.
This also rewrites the text in the Alternatives section to include guidance on how to deal with zone transfers scalability and tailored responses (based on GeoIP for example).
Tagging @moonshiner (who suggested the move) and @fanf2 (as original editor of the Alternatives section) to seek comments on the change. I plan to merge this on Monday if I receive no pushback.
This PR closes #40 and and maybe also #35 and #36.
This moves the informative guidance text for alternative setups to an appendix. The reason for this is that this text is not required for the ANAME protocol but provides useful information for providers that use a non-traditional DNS architecture.
This also rewrites the text in the Alternatives section to include guidance on how to deal with zone transfers scalability and tailored responses (based on GeoIP for example).
Tagging @moonshiner (who suggested the move) and @fanf2 (as original editor of the Alternatives section) to seek comments on the change. I plan to merge this on Monday if I receive no pushback.
This PR closes #40 and and maybe also #35 and #36.