Azure / Azure/azure-quickstart-templates
301-dns-forwarder/post-template-deployment query
- Dominant language
- Bicep
- Stars
- 14.9k
- Forks
- 16.2k
- Avg merge
- 6d 21h
- Merged PRs (30d)
- 6
Description
--------------------MESSAGE FROM ADMIN, DELETE BEFORE SUBMITTING----------------------
Sorry to hear you had a bad experience with one of the templates :worried: But, in case you're just asking a question, we're happy to help. You can also check if the question might already have been asked here https://github.com/Azure/azure-quickstart-templates/issues?utf8=%E2%9C%93&q=is%3Aissue
We've created an outline of recommended sections to fill out that will help make this Pull Request awesome!
--------------------MESSAGE FROM ADMIN, DELETE BEFORE SUBMITTING----------------------
[301-dns-forwarder](https://github.com/Azure/azure-quickstart-templates/tree/master/301-dns-forwarder)
### Issue Details
I tried to deploy this template. is there post deployment will needed to be configured?
### Repro steps (*if necessary, delete otherwise*)
1. Deployed the template
2. Let it running
3. Configure on-prem dns for Forward Query to the DNS Forwarder VM in Azure
4. No other configuration. Upon checking seems bind9 didnt get configured
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the 301-dns-forwarder template linked in the issue and review its deployment steps and outputs. Reproduce the deployment, then check the reported on-premises DNS forwarding setup and whether bind9 is configured; done means documenting the required post-deployment configuration or identifying the template issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100