From 38e45f9641c828bd4fc38f53708ae61dbe28cf7e Mon Sep 17 00:00:00 2001 From: Brian Shumate Date: Wed, 28 Sep 2016 12:20:36 -0400 Subject: [PATCH 1/2] Update getting started/join to address #2204 --- website/source/intro/getting-started/join.html.markdown | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/website/source/intro/getting-started/join.html.markdown b/website/source/intro/getting-started/join.html.markdown index 67f410637b..eb28ee3272 100644 --- a/website/source/intro/getting-started/join.html.markdown +++ b/website/source/intro/getting-started/join.html.markdown @@ -56,9 +56,10 @@ command-line option](/docs/agent/options.html#_node). We will also specify a [`bind` address](/docs/agent/options.html#_bind): this is the address that Consul listens on, and it *must* be accessible by all other nodes in the cluster. While a `bind` address is not strictly -necessary (Consul will by default listen on the first private IP on a -system), it's always best to provide one. Production servers often have -multiple interfaces, so specifying a `bind` address assures that you will +necessary, it's always best to provide one. Consul will by default attempt to +listen on the first private IP on a system, but will fail to start with an +error if multiple private IPs are found. Since production servers often +have multiple interfaces, specifying a `bind` address assures that you will never bind Consul to the wrong interface. The first node will act as our sole server in this cluster, and we indicate From d8080c27d5b21694b45eaa818e07ada25a888dca Mon Sep 17 00:00:00 2001 From: Brian Shumate Date: Thu, 29 Sep 2016 12:42:22 -0400 Subject: [PATCH 2/2] correction --- website/source/intro/getting-started/join.html.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/source/intro/getting-started/join.html.markdown b/website/source/intro/getting-started/join.html.markdown index eb28ee3272..b0a8f7d32e 100644 --- a/website/source/intro/getting-started/join.html.markdown +++ b/website/source/intro/getting-started/join.html.markdown @@ -57,7 +57,7 @@ We will also specify a [`bind` address](/docs/agent/options.html#_bind): this is the address that Consul listens on, and it *must* be accessible by all other nodes in the cluster. While a `bind` address is not strictly necessary, it's always best to provide one. Consul will by default attempt to -listen on the first private IP on a system, but will fail to start with an +listen on all IPv4 interfaces on a system, but will fail to start with an error if multiple private IPs are found. Since production servers often have multiple interfaces, specifying a `bind` address assures that you will never bind Consul to the wrong interface.