Temporary failure in name resolution causing severe problems running embassy

[da-kami]

This is a follow up of #7 and #3.

When debugging not being able to resolve the UI URL for the ItchySats service (#7) I noticed that I still kept seeing the Temporary failure in name resolution problem that I reported in #3.
I noticed that this problem actually affects the whole system, somehow the nameserver is not configured correctly which results

This not only has an affect on ItchySats, but on the whole system. Notably, bitcoind eventually started running into sync problems because the reported system time was incorrect (i.e. in the past) because due to not being able to properly resolve names the raspi was unable to sync with the time server.

Note: I had ran into the Temporary failure in name resolution problem when using the embassy with multiple different routers. I don't exactly understand what is causing this issue. I did not have such kind of issues with my Umbrel node (or any other of my raspberries).

---

Eventually I was able to overcome this problem by manually configuring a nameserver on the embassy:

sudo sh -c 'echo "nameserver 8.8.8.8" >> /etc/resolv.conf'

Once DNS was properly working again all the problems went away. Bitcoind worked properly again and I could resolve the service URL.
I tried to configure the nameserver more permanently by installing resolveconf (as described in this tutorial) but somehow /etc/resolv.conf does not reflect the configured nameserver.
I can still overcome the problem by manually adding the nameserver to resolv.conf but I have to do that after each restart otherwise the system time is incorrect and resolving names might not work.

Does the embassy configure it's own DNS that overwrites /etc/resolv.conf?
What could cause this problem?

[dr-bonez]

This should be fixed by Start9Labs/start-os#1741