Hi @mike-miller-ct,
It looks like there might be an issue with networking on that host.
As I mentioned over in Meaning of "Failed to resolve consul-consul-server-0.consul-consul-server.consul.svc" - #3 by mike-miller-ct, it looks like one of the problems is that the node cannot resolve the DNS hostnames for the other Consul servers. Have you tried execing into the pod and executing a few queries to see if you’re manually able to resolve and contact this hostname?
Here’s a few commands you can run to test basic connectivity.
$ cat /etc/resolv.conf
search consul.svc.cluster.local svc.cluster.local cluster.local
nameserver 10.43.0.10
options ndots:5
$ nslookup hashicorp-consul-server-0.hashicorp-consul-server.consul.svc.cluster.local
Server: 10.43.0.10
Address: 10.43.0.10:53
Name: hashicorp-consul-server-0.hashicorp-consul-server.consul.svc.cluster.local
Address: 10.42.4.75
$ ping -c1 hashicorp-consul-server-0.hashicorp-consul-server.consul.svc
PING hashicorp-consul-server-0.hashicorp-consul-server.consul.svc.cluster.local (10.42.4.75) 56(84) bytes of data.
64 bytes from hashicorp-consul-server-0.hashicorp-consul-server.consul.svc.cluster.local (10.42.4.75): icmp_seq=1 ttl=64 time=0.075 ms
--- hashicorp-consul-server-0.hashicorp-consul-server.consul.svc.cluster.local ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.075/0.075/0.075/0.000 ms
Also, is the IP address you’re specifying in consul join the address of another server or client in the environment?