From fbbb765bf93cf4f016b7a5d16c31e16515d70c90 Mon Sep 17 00:00:00 2001 From: Ryan Breen Date: Sat, 31 Jan 2015 13:07:21 -0500 Subject: [PATCH] More heavy-handed reorg of content for flow. --- website/source/docs/agent/dns.html.markdown | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/website/source/docs/agent/dns.html.markdown b/website/source/docs/agent/dns.html.markdown index b3ac4e7bf7..511e536d9f 100644 --- a/website/source/docs/agent/dns.html.markdown +++ b/website/source/docs/agent/dns.html.markdown @@ -15,15 +15,15 @@ discovery without any high-touch integration with Consul. For example, instead of making HTTP API requests to Consul, a host can use the DNS server directly via name lookups like "redis.service.east-aws.consul". This query automatically -translates to a lookup of nodes that provide the redis service -are located in the "east-aws" datacenter and have no failing health checks. +translates to a lookup of nodes that provide the redis service, +are located in the "east-aws" datacenter, and have no failing health checks. It's that simple! -There are a number of [configuration options](/docs/agent/options.html) that -are important for the DNS interface. They are `client_addr`, `ports.dns`, `recursors`, -`domain`, and `dns_config`. By default, Consul will listen on 127.0.0.1:8600 for DNS queries -in the "consul." domain, without support for DNS recursion. All queries are case-insensitive, -so a lookup of `PostgreSQL.node.dc1.consul` will find all nodes named `postgresql`. +There are a number of configuration options that are important for the DNS interface, +specifically `client_addr`, `ports.dns`, `recursors`, `domain`, and `dns_config`. By default, +Consul will listen on 127.0.0.1:8600 for DNS queries in the "consul." domain, without support +for further DNS recursion. Please consult the [documentation on configuration options](/docs/agent/options.html) +for more details. There are a few ways to use the DNS interface. One option is to use a custom DNS resolver library and point it at Consul. Another option is to set Consul @@ -35,6 +35,9 @@ You can experiment with Consul's DNS server on the command line using tools such $ dig @127.0.0.1 -p 8600 redis.service.dc1.consul. ANY +Note that in DNS, all queries are case-insensitive. A lookup of `PostgreSQL.node.dc1.consul` +will find all nodes named `postgresql`. + ## Node Lookups To resolve names, Consul relies on a very specific format for queries.