I’m having this same problem too. From everything I can see the underlying issue is in the go gRPC library with the method it uses to resolve DNS names. And I know it’s specific to gRPC since the servers connect to mosquitto and postgresql just fine which also use DNS names, but fail when trying to use gRPC to communicate between chirpstack programs.
Hello, is this problem solved? i’ve download the docker version 3 days ago and while the centos is not connected to internet, it’s not possible to add a network server with the GUI (even if i use "chirpstack-network-server:8000) but with my machine is connected to internet, no problem.
how to know which version of alpine is use in my images?
/ # ping chirpstack-application-server
PING chirpstack-application-server (172.28.0.6): 56 data bytes
64 bytes from 172.28.0.6: seq=0 ttl=64 time=0.890 ms
64 bytes from 172.28.0.6: seq=1 ttl=64 time=0.754 ms
--- chirpstack-application-server ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0.754/0.822/0.890 ms
/ # nslookup chirpstack-application-server
nslookup: can't resolve '(null)': Name does not resolve
Address 1: 172.28.0.6 chirpstack-application-server.internal-network
/ # arp -a
postgresql.internal-network (172.28.0.2) at 02:42:ac:1c:00:02 [ether] on eth0
? (172.28.0.1) at 02:42:c8:05:8c:d0 [ether] on eth0
chirpstack-application-server.internal-network (172.28.0.6) at 02:42:ac:1c:00:06 [ether] on eth0
mosquitto.internal-network (172.28.0.5) at 02:42:ac:1c:00:05 [ether] on eth0
redis.internal-network (172.28.0.8) at 02:42:ac:1c:00:08 [ether] on eth0