-
Notifications
You must be signed in to change notification settings - Fork 11
Description
Describe the bug
While connected locally, VPN or wifi dappnode cannot resolve DNS related names such as my.dappnode rocketpool and brain/web3signer, rendering them inaccessible.
The main dappnode dashboard, web3signer gnosis and rocketpool can be accessed via the container IP, however rocketpool UI does not work this way since it still tries to fetch it's resources through the default URL, which it isn't able to resolve...
When I connect locally I am able to navigate to dappnode.local successfully but other DNS addresses continue to not resolve.
Things I have tried
I have tried to fetch and older version of BIND and install it manually however I get this error:

I have done a full reinstall of dappnode on my machine and the problem still persists.
To Reproduce
- Connect via VPN or Wifi to dappnode
- Navigate to my.dappnode
- See error-->
Expected behavior
User should be able to connect successfully to resolved DNS addresses on dashboard and other packages
Screenshots
DAppNode version:
Core DAppNode Packages versions
bind.dnp.dappnode.eth: 0.2.11
dappmanager.dnp.dappnode.eth: 0.2.86, commit: ad99085d
https.dnp.dappnode.eth: 0.2.1
ipfs.dnp.dappnode.eth: 0.2.22
wifi.dnp.dappnode.eth: 0.2.9
wireguard.dnp.dappnode.eth: 0.1.3
System info
dockerComposeVersion: 2.21.0
dockerServerVersion: 24.0.7
dockerCliVersion: 24.0.7
os: ubuntu
versionCodename: jammy
architecture: amd64
kernel: 6.5.0-27-generic
Disk usage: 27%
Hardware: ASUS TUF Gaming Laptop
OS: Ubuntu 22.04 - Dappnode Install from Script
Additional context
This is an emergency - my ETH is stuck in my rocketpool and I have no UI to interface with it and exit my validator.

