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

DNS resolution flow incomplete #745

Closed
FabienGilbert opened this issue Sep 2, 2022 · 0 comments · Fixed by #746
Closed

DNS resolution flow incomplete #745

FabienGilbert opened this issue Sep 2, 2022 · 0 comments · Fixed by #746
Labels
bug Something isn't working

Comments

@FabienGilbert
Copy link
Contributor

Description

All of the Virtual Networks get deployed configured with default Azure DNS. The Private DNS zones that get deployed in the Hub for AMPLS and Blob storage are not resolvable from the other tiers. Furthermore, most dev customers have Active Directory and DNS servers in their environments, so they need a hybrid DNS resolution flow.

Steps to Reproduce

Steps to reproduce the behavior:

  1. Deploy MLZ
  2. Try to resolve a private endpoint (AMPLS' for instance) from a tier 1, 2 or 3

Expected behavior

Azure Monitor should resolve to the AMPLS private IP address from tier 1+

Actual behavior

Azure Monitor resolves to a public endpoint from tier 1+

Screenshots

Additional context

Operating System: W11
Terraform Version:
Cloud (public, Azure Government, etc.): MAC and MAG

@FabienGilbert FabienGilbert added the bug Something isn't working label Sep 2, 2022
@FabienGilbert FabienGilbert mentioned this issue Sep 2, 2022
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant