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.

Sign up for GitHub

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

Jump to bottom

fix: Fix typo #395

Merged
merged 1 commit into from
Sep 6, 2024
Merged

fix: Fix typo #395

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions azure-resources/Network/privateDnsZones/recommendations.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@
- name: Azure Monitor Baseline Alerts - privateDnsZones
url: "https://azure.github.io/azure-monitor-baseline-alerts/services/Network/privateDnsZones/"

- description: Use regional Private DNS Zones when there is a low recovery time objective(RTO) requirement
- description: Use regional Private DNS Zones when there is a low recovery time objective (RTO) requirement
aprlGuid: 1e02335c-1f90-fd4e-a5a5-d359c7b22d70
recommendationTypeId: null
recommendationControl: Disaster Recovery
Expand All @@ -63,7 +63,7 @@
recommendationResourceType: Microsoft.Network/privateDnsZones
recommendationMetadataState: Active
longDescription: |
Azure Private DNS allows the Time-To-Live (TTL) for record sets in the zone to be set to a value between 1 and 2147483647 seconds. You should ensure that the TTL for the DNS record sets in your DNS Zones are set appropriately to meet your RPO targets,
Azure Private DNS allows the Time-To-Live (TTL) for record sets in the zone to be set to a value between 1 and 2147483647 seconds. You should ensure that the TTL for the DNS record sets in your DNS Zones are set appropriately to meet your RPO targets.
potentialBenefits: Ensures that no cached DNS records exist past RPO targets
pgVerified: false
publishedToLearn: false
Expand Down