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

Update segments.html.markdown.erb

This commit is contained in:
James Phillips 2017-09-06 16:42:13 -07:00 committed by GitHub
parent 69bebb2a99
commit 87eeec254f
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/guides/segments.html.markdown.erb
View File

@ -57,7 +57,7 @@ linking the different segments together. The configured list of segments is spec
another segment, or the listening port of another segment on a server, they will get a segment mismatch error. another segment, or the listening port of another segment on a server, they will get a segment mismatch error.
Once the servers have been configured with the correct segment info, the clients only need to specify Once the servers have been configured with the correct segment info, the clients only need to specify
their own segment in the [Agent Config](/docs/agent/options.html) and join by connecting to another their own segment in the [Agent Config](/docs/agent/options.html#_segment) and join by connecting to another
agent within the same segment. If joining to a Consul server, client will need to provide the server's agent within the same segment. If joining to a Consul server, client will need to provide the server's
port for their segment along with the address of the server when performing the join (for example, port for their segment along with the address of the server when performing the join (for example,
`consul agent -retry-join "consul.domain.internal:1234"`). `consul agent -retry-join "consul.domain.internal:1234"`).
@ -233,4 +233,4 @@ redis.query.consul. 0 IN SRV 1 1 9000 client2.node.dc1.consul.
;; ADDITIONAL SECTION: ;; ADDITIONAL SECTION:
client2.node.dc1.consul. 0 IN A 192.168.0.6 client2.node.dc1.consul. 0 IN A 192.168.0.6
``` ```