[v16] Remove TXT record validation of custom DNS zones in VNet #46722
+40
−226
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Nic Klaassen <nic@goteleport.com>
github-actions
bot
added
backport
documentation
rfd
github-actions
bot
requested review from
nklaassen,
ravicious and
rosstimothy
rosstimothy
approved these changes
Sep 18, 2024
avatus
approved these changes
Sep 18, 2024
public-teleport-github-review-bot
bot
removed request for
ravicious and
nklaassen
|
🤖 Vercel preview here: https://docs-h7js6278f-goteleport.vercel.app/docs/ver/preview |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport #46709 to branch/v16
changelog: Removed TXT record validation from custom DNS zones in VNet; VNet now supports any custom DNS zone, as long as it's included in
vnet_config