Azure / Azure/HubAndSpokeResearchEnclave
When not using an AD domain, create a private DNS zone for VM record registration
- Dominant language
- Bicep
- Stars
- 18
- Forks
- 18
- Avg merge
- 4d 19h
- Merged PRs (30d)
- 3
Description
The private DNS zone name will be a new parameter and an example could be `research.aelterman.cloud`. Auto-registration will be enabled for virtual networks linked to this zone.
This needs to be created in the hub and linked to both the hub and the spoke networks.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the repository's Bicep entry point for the hub-and-spoke network and identify how parameters and virtual-network links are defined. Add the private DNS zone name parameter, create the zone in the hub, enable auto-registration, and link it to both hub and spoke networks. Done means deployments without an AD domain register VM records through the new zone.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, networking
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100