Update DNS to reflect decision point #127274
Conversation
Added a note to help customers land on the decision faster. Minor language changes
Update native-dns-forward-lookup-zone.md
|
@sblair01 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Hi @sblair01 - This pull request was opened in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. We can keep this PR open for review and merge, but would you make future content updates in the private repo? Thank you! @ jjaygbay1 Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
|
Learn Build status updates of commit c5d17b8: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
|
@sblair01 Please move this PR to a private repo and add me as reviewer. |
|
@sblair01 Microsoft authors and contributors need to make content contributions through the private repository so the content can be staged and validated by the current validation rules. After you make your changes in the private repo, review the articles on staging, and fix any validation issues, you can add the sign-off comment to let PR reviewers know that the updates are ready to be merged. Read about authors working in the public repo for more information. If you need help getting set up to work in the private repo, see Get started contributing to the Microsoft Learn platform. Thank you. |
| 2. In the Search the Marketplace field, type Private DNS Resolver and click Enter. | ||
| 3. Click Create for the Private DNS Resolver. | ||
| 4. Ensure the Subscription, Resource group, and Region fields are correct. Enter a name and choose your Virtual Network. This network must be the same as the one where you deployed your private cloud; then, click Next: Inbound Endpoints. | ||
| 5. Click 'Add an Endpoint', enter a name for the Inbound endpoint (e.g., dns-in), select the subnet for the DNS inbound endpoint, and click 'Save'. |
There was a problem hiding this comment.
| 5. Click 'Add an Endpoint', enter a name for the Inbound endpoint (e.g., dns-in), select the subnet for the DNS inbound endpoint, and click 'Save'. | |
| 5. Click 'Add an Endpoint', enter a name for the Inbound endpoint, such as dns-in, and select the subnet for the DNS inbound endpoint, and click 'Save'. |
Style guide
| 6. Click Next: Outbound Endpoints. | ||
| 7. Click Add an Endpoint, enter a name for the Outbound endpoint, such as dns-out and select the subnet for the DNS outbound endpoint and click Save. | ||
| 7. Click "Add an Endpoint," enter a name for the Outbound endpoint (e.g., dns-out), select the subnet for the DNS outbound endpoint, and click "Save." |
There was a problem hiding this comment.
| 7. Click "Add an Endpoint," enter a name for the Outbound endpoint (e.g., dns-out), select the subnet for the DNS outbound endpoint, and click "Save." | |
| 7. Click "Add an Endpoint," enter a name for the Outbound endpoint, such as dns-out and select the subnet for the DNS outbound endpoint, and click "Save." |
|
The article has been substantially updated since this PR was opened. If you'd like to update the article in its current state, please open a new PR in the private repo. #please-close |
This PR points users quickly on when to use public DNS and the benefit. The PR also incorporates minor language changes. The PR also incorporates minor language changes