status-im
/
consul
mirror of https://github.com/status-im/consul.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Restructure opening paragraphs to have better flow.

This commit is contained in:
Ryan Breen 2015-01-31 13:01:00 -05:00
parent a7357aae65
commit 7a0515817a
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
website/source/docs/agent/dns.html.markdown
View File

@ -10,14 +10,14 @@ description: |-
One of the primary query interfaces for Consul is DNS. One of the primary query interfaces for Consul is DNS.
The DNS interface allows applications to make use of service The DNS interface allows applications to make use of service
discovery without any high-touch integration with Consul. For discovery without any high-touch integration with Consul.
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 For example, instead of making HTTP API requests to Consul,
provide the redis service, are located in the "east-aws" datacenter, a host can use the DNS server directly via name lookups
and have no failing health checks. It's that simple! 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.
It's that simple!
There are a number of [configuration options](/docs/agent/options.html) that 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`, are important for the DNS interface. They are `client_addr`, `ports.dns`, `recursors`,