Add fullnode.dappnode domain to docker DNS

[pablomendezroyo]

According to the upcoming deletion of the BIND package and the switch to use the native docker DNS has been added the corresponding settings needed (alias fullnode.dappnode) to the fullnode feature.

• Add migration to ethClient module:
• Remove/add alias fullnode.dappnode in the compose when necessary
• Disconnect/connect package to update the alias
• Create new editor compose funcions: addAlias and removeAlias (might be necessary in the future since the alias will be the new endpoint used)
• Remove unnecesary funcions
• Add unit tests to compose editor

[github-actions]

🚀 Deployed on https://60ddbc6860e84ff776759f4c--objective-borg-9eeae5.netlify.app

[github-actions]

DAppNode bot has built and pinned the release to an IPFS node, for commit: 5a941f2

This is a development version and should only be installed for testing purposes, install link

/ipfs/QmXogAHmfn2v5nrhCASb6CnUdfcsNJUgx5ddxkd3h3fxtC

(by dappnodebot/build-action)

[dapplion]

While this PR solves the issue with fullnode.dappnode it doesn't address the underlying issue where the logic to handle BIND mappings and docker DNS alias is duplicated. A long term sustainable solution would involve to merge those entities so whenever a consumer wants to manipulate domains it affects everything automatically.

[pablomendezroyo]

While this PR solves the issue with fullnode.dappnode it doesn't address the underlying issue where the logic to handle BIND mappings and docker DNS alias is duplicated. A long term sustainable solution would involve to merge those entities so whenever a consumer wants to manipulate domains it affects everything automatically.

Should I think already on this, or open an issue for the near future

[dapplion]

While this PR solves the issue with fullnode.dappnode it doesn't address the underlying issue where the logic to handle BIND mappings and docker DNS alias is duplicated. A long term sustainable solution would involve to merge those entities so whenever a consumer wants to manipulate domains it affects everything automatically.

Should I think already on this, or open an issue for the near future

The earliest we find a solution the less risk of having bugs like this