hashicorp / hashicorp/consul

cannot resolve domain/FQDN while joining a exist cluster

Open
#1,507 13 comments 0 reactions 1 assignee Claimed by @slackpad View on GitHub
theme/internal-cleanup type/bug
Dominant language
Go
Stars
30.1k
Forks
4.6k
Avg merge
2d 6h
Merged PRs (30d)
43

Description

I use following CLI to start a consul server to join a exist cluster.

``` bash
$ ping node1
PING node1 (192.168.1.21): 56 data bytes
64 bytes from 192.168.1.21: icmp_seq=0 ttl=64 time=0.053 ms
64 bytes from 192.168.1.21: icmp_seq=0 ttl=64 time=0.053 ms
...

$ consul agent -server -node node2 -retry-join node1
```

errorlogs (**the resolved ip address is wrong**)

```
2015/12/14 06:45:23 [INFO] agent: (LAN) joined: 0 Err: dial tcp 220.250.64.225:8301: i/o timeout
2015/12/14 06:45:23 [WARN] agent: Join failed: dial tcp 220.250.64.225:8301: i/o timeout, retrying in 30s
```

That is failed to join the node2 to node1 cluster.
If I changes node1 to 192.168.1.21, that does work.

``` bash
$ consul agent -server -node node2 -retry-join 192.168.1.21
```

My consul version is 0.5.2

Also, `consul join ` does not work.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.