diff --git a/website/content/docs/services/discovery/dns-configuration.mdx b/website/content/docs/services/discovery/dns-configuration.mdx
index 06c9e2895e..e70674e46b 100644
--- a/website/content/docs/services/discovery/dns-configuration.mdx
+++ b/website/content/docs/services/discovery/dns-configuration.mdx
@@ -33,8 +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.
 
-> [!WARNING]  
-> We recommend configuring your DNS resolvers to point the `consul.` domain towards your Consul DNS server(s). Misconfigurations can result in queries for the `consul.` domain being routed 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 Consul 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.