From ac5af9bcbc29446d60d83586088ef3f059a69125 Mon Sep 17 00:00:00 2001 From: Jeff Wang Date: Wed, 23 Sep 2015 23:09:38 -0700 Subject: [PATCH 1/2] Make node lookup DNS documentation consistent --- website/source/docs/agent/dns.html.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/source/docs/agent/dns.html.markdown b/website/source/docs/agent/dns.html.markdown index 11b0ab613..0c3a3055a 100644 --- a/website/source/docs/agent/dns.html.markdown +++ b/website/source/docs/agent/dns.html.markdown @@ -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. A node lookup, a simple query for the address of a named node, looks like this: - .node.. + .node[.datacenter]. 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 From 75c21693a8d4d49b1786084dae38cf10e2d4e62a Mon Sep 17 00:00:00 2001 From: Jeff Wang Date: Wed, 23 Sep 2015 23:16:34 -0700 Subject: [PATCH 2/2] Make service lookup DNS documentation consistent --- website/source/docs/agent/dns.html.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/source/docs/agent/dns.html.markdown b/website/source/docs/agent/dns.html.markdown index 0c3a3055a..cf148039e 100644 --- a/website/source/docs/agent/dns.html.markdown +++ b/website/source/docs/agent/dns.html.markdown @@ -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: - [tag.].service[.datacenter][.domain] + [tag.].service[.datacenter]. 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