-
Notifications
You must be signed in to change notification settings - Fork 146
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
Documentation for name resolution (DNS) within landing zones #353
Labels
documentation
Improvements or additions to documentation
Comments
Potentially related to this question that was recently asked: #674 |
This can be resolved by #746 |
Repository owner
moved this from Future Backlog
to Done
in Mission Landing Zone 2022
Sep 20, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Benefit/Result/Outcome
So that IT Administrators have guidance on implementing DNS as it applies to their specific scenario.
Description
We considered options for auto-deployment for at least one DNS scenario, however, we believe that the best name resolution solution will depend on how external traffic is configured and connected to the landing zone. Therefore, we believe the best option for MLZ customers is to document the most likely scenarios.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: