Skip to content

Commit b990789

Browse files
committed
grammar
1 parent 37bb360 commit b990789

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/dns/private-resolver-hybrid-dns.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -25,9 +25,9 @@ The [Azure DNS Private Resolver](dns-private-resolver-overview.md) is a service
2525

2626
Benefits of using the Azure DNS Private Resolver service vs. VM-based resolvers or DDI solutions include:
2727
- Zero maintenance: Unlike VM or hardware based solutions, the private resolver doesn't require software updates, vulnerability scans, or security patching. The private resolver service is fully managed.
28-
- Cost reduction: Azure DNS Private Resolver is a multi-tenant service and can cost a fraction of the expense required to use and license multiple VM-based DNS resolvers.
29-
- High availability: The Azure DNS Private Resolver service has built-in high availability features. The service is [availability zone](/azure/availability-zones/az-overview) aware, thus ensuring high availability and redundancy of your DNS solution can be accomplished much less effort. For more information on how to configure DNS failover using the private resolver service, see [Tutorial: Set up DNS failover using private resolvers](tutorial-dns-private-resolver-failover.md).
30-
- DevOps friendly: Traditional DNS solutions are hard to integrate with DevOps workflows as these often require manual configuration for every DNS change. Azure DNS private resolver provides a fully functional ARM interface, which can be easily integrated with DevOps workflows.
28+
- Cost reduction: Azure DNS Private Resolver is a multi-tenant service and can cost a fraction of the expense required to use and license multiple VM-based DNS resolvers, or deploy DDI devices.
29+
- High availability: The Azure DNS Private Resolver service has built-in high availability features. The service is [availability zone](/azure/availability-zones/az-overview) aware, thus ensuring that high availability and redundancy of your DNS solution can be accomplished with much less effort. For more information on how to configure DNS failover using the private resolver service, see [Tutorial: Set up DNS failover using private resolvers](tutorial-dns-private-resolver-failover.md).
30+
- DevOps friendly: Traditional DNS solutions are hard to integrate with DevOps workflows as these often require manual configuration for every DNS change. Azure DNS private resolver provides a fully functional ARM interface that can be easily integrated with DevOps workflows.
3131

3232
## DNS forwarding ruleset
3333

0 commit comments

Comments
 (0)