diff --git a/website/source/docs/guides/performance.html.markdown b/website/source/docs/guides/performance.html.markdown
index dc42d406a2..c33c3bebca 100644
--- a/website/source/docs/guides/performance.html.markdown
+++ b/website/source/docs/guides/performance.html.markdown
@@ -78,8 +78,9 @@ or add more powerful servers.
 
 * For DNS-heavy workloads, configuring all Consul agents in a cluster with the
 [`allow_stale`](/docs/agent/options.html#allow_stale) configuration option will allow reads to
-scale across all Consul servers, not just the leader. See [Stale Reads](/docs/guides/dns-cache.html#stale)
-in the [DNS Caching](/docs/guides/dns-cache.html) guide for more details. It's also good to set
+scale across all Consul servers, not just the leader. Consul 0.7 and later enables stale reads
+for DNS by default. See [Stale Reads](/docs/guides/dns-cache.html#stale) in the
+[DNS Caching](/docs/guides/dns-cache.html) guide for more details. It's also good to set
 reasonable, non-zero [DNS TTL values](/docs/guides/dns-cache.html#ttl) if your clients will
 respect them.