Update website/content/docs/services/discovery/dns-configuration.mdx

Co-authored-by: Blake Covarrubias <blake@covarrubi.as>
6 months ago · 995e9a8e25
parent 28315fda69
commit 995e9a8e25
1 changed files with 1 additions and 1 deletions
--- a/website/content/docs/services/discovery/dns-configuration.mdx
+++ b/website/content/docs/services/discovery/dns-configuration.mdx
@ -33,7 +33,7 @@ You can specify a list of addresses in the agent's [`recursors`](/consul/docs/ag

 Nodes that query records outside the `consul.` domain resolve to an upstream DNS. You can specify IP addresses or use `go-sockaddr` templates. Consul resolves IP addresses in the specified order and ignores duplicates.

-We recommend that you configure DNS resolvers to point the `consul.` domain towards your Consul DNS servers. Misconfigurations may cause Consul to route queries for the `consul.` domain outside of your network instead, leaking DNS queries to root DNS servers.
+We recommend that you configure DNS resolvers to point the `consul.` domain towards your Consul DNS servers. Misconfigurations may cause other DNS infrastructure to route queries for the `consul.` domain outside of your network instead, leaking DNS queries to root DNS servers.

 ### Enable non-Consul queries
 You enable non-Consul queries to be resolved by setting Consul as the DNS server for a node and providing a [`recursors`](/consul/docs/agent/config/config-files#recursors) configuration.