dappnode / DAppNode

General repository of the project dappnode
GNU General Public License v3.0
585 stars 103 forks source link

Package DNS names don't resolve on dappnode host #160

Open TripleSpeeder opened 4 years ago

TripleSpeeder commented 4 years ago

DNS names resolve fine on systems connected to the DAppNode VPN. But on the DAppNode host itself DNS names like fullnode.dappnode do not resolve:

[michael@stingray ~]$ ping fullnode.dappnode
PING fullnode.dappnode (172.33.0.3) 56(84) bytes of data.
64 Bytes von 172.33.0.3 (172.33.0.3): icmp_seq=1 ttl=63 Zeit=0.481 ms
^C
--- fullnode.dappnode ping statistics ---
1 Pakete übertragen, 1 empfangen, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.481/0.481/0.481/0.000 ms
[michael@stingray ~]$ ssh -l dappnode dappnode
...
dappnode@dappnode:~$ ping fullnode.dappnode
ping: fullnode.dappnode: Name or service not known
dappnode@dappnode:~$ ping fullnode
ping: fullnode: Name or service not known
dappnode@dappnode:~$ 

/etc/resolv.conf on the dappnode host:

domain fritz.box
search fritz.box
nameserver 192.168.178.1

Core DAppNode Packages versions

System info

┆Issue is synchronized with this Basecamp todo by Unito

dapplion commented 3 years ago

@eduadiez Is it possible to solve this issue? I miss this feature too sometimes

dapplion commented 3 years ago

@3alpha could you investigate if is there any feasible solution for this? :pray:

3alpha commented 3 years ago

We could expose DAppNode's DNS to the host, but I don't know whether that would introduce new issues. (I don't believe so, but needs to be tested)

However, that wouldn't resolve issue because Docker's internal network isn't by default available from anywhere and that includes host machine.