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 Identity VNET to each Private DNS zone's Virtual network links #733

Closed
paullizer opened this issue Aug 2, 2022 · 0 comments · Fixed by #791 or #796
Closed

Add Identity VNET to each Private DNS zone's Virtual network links #733

paullizer opened this issue Aug 2, 2022 · 0 comments · Fixed by #791 or #796

Comments

@paullizer
Copy link

paullizer commented Aug 2, 2022

Benefit/Result/Outcome

When a customer deploys a DNS solution, like a Domain Controller or Infoblox, the DNS solution fails to work. The customer needs to manually add the identity VNET to the Private DNS Zone.

Description

The identity VNET is not added to the Virtual network links for the various Private DNS zones.

Acceptance Criteria

  • Identity VNET is added to each private DNS zone during deployment.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment