Azure / Azure/azure-quickstart-templates
Add vnet parameters to dns-forwarder template in order to avoid ip range conflicts
Nobody has claimed this yet.
- Dominant language
- Bicep
- Stars
- 14.9k
- Forks
- 16.2k
- Avg merge
- 6d 21h
- Merged PRs (30d)
- 6
Description
Issue Details
I am new to Azure DNS, but I have already set up my network infrastructure (Hub-Spoke) in Azure when it comes to VNets und Subnets. Hence, I would like to use my existing VNets in the template.
Therefore, the following variables should be editable parameters so that they can be filled in in the creation wizard when deyploying via Azure Portal UI:
- "asetName": "dnsproxy-avail",
- "nsgName": "dnsproxy-nsg",
- "vnetName": "dnsproxy-vnet",
- "vnetAddressPrefix": "10.0.0.0/8",
- "subNet1Name": "subnet1",
- "subNet1Prefix": "10.1.0.0/16",
Otherwise the created dnsproxy-vnet conflicts with the IP ranges from my other VNets.
Making the names parameters would also help to adhere to company naming convention for Azure resources.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the DNS Forwarder VM template linked in the issue and inspect how asetName, nsgName, vnetName, vnetAddressPrefix, subNet1Name, and subNet1Prefix are currently defined. Done means these values can be supplied as deployment parameters so existing network ranges and organizational resource naming conventions can be used without conflicts.
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
- 38/100