luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

Merge pull request #1258 from jeffawang/master 

website: Make the DNS Interface documentation notation consistent with functionality
This commit is contained in:
Ryan Breen 2015-09-24 08:43:32 -04:00
parent 719f16d16b 75c21693a8
commit 69d1253a3f
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -48,7 +48,7 @@ To resolve names, Consul relies on a very specific format for queries.
There are fundamentally two types of queries: node lookups and service lookups. There are fundamentally two types of queries: node lookups and service lookups.
A node lookup, a simple query for the address of a named node, looks like this: A node lookup, a simple query for the address of a named node, looks like this:
<node>.node.<datacenter>.<domain> <node>.node[.datacenter].<domain>
For example, if we have a "foo" node with default settings, we could look for For example, if we have a "foo" node with default settings, we could look for
"foo.node.dc1.consul." The datacenter is an optional part of the FQDN: if not "foo.node.dc1.consul." The datacenter is an optional part of the FQDN: if not
@ -90,7 +90,7 @@ two lookup methods: standard and strict [RFC 2782](https://tools.ietf.org/html/r
The format of a standard service lookup is: The format of a standard service lookup is:
[tag.]<service>.service[.datacenter][.domain] [tag.]<service>.service[.datacenter].<domain>
The `tag` is optional, and, as with node lookups, the `datacenter` is as well. If no tag is The `tag` is optional, and, as with node lookups, the `datacenter` is as well. If no tag is
provided, no filtering is done on tag. If no datacenter is provided, the datacenter of provided, no filtering is done on tag. If no datacenter is provided, the datacenter of