Acme-dns not reachable, possible DNS problems, "couldn't get address for"

[CoUsT]

@JamesLE

is it possible you were trying to run acme-dns as a non- root user, but without the CAP_NET_BIND_SERVICE capability that lets non- root processes bind to low port numbers

I executed all my commands as root user. I also used the service file and instructions from the readme of acme-dns repo so that it starts automatically on boot.

@JamesLE

or maybe using some kind of containerization that abstracts the external IP you want to listen on, so that the acme-dns process can't find its interface?

All was done on a fresh installation of Ubuntu 20.04 LTS tested on both Google Cloud and Oracle Cloud instances.

I tried again just to be sure and this is the outcome:

Jul 05 13:02:37 vpn acme-dns[10837]: time="2021-07-05T13:02:37Z" level=info msg="Listening DNS" addr="130.61.122.175:53" proto=tcp4
Jul 05 13:02:37 vpn acme-dns[10837]: time="2021-07-05T13:02:37Z" level=fatal msg="listen tcp4 130.61.122.175:53: bind: cannot assign requested address"

EDIT:

@Osiris

However, perhaps the host is behind NAT and the public IP address shouldn't be used? Instead, perhaps the internal private IP has to be used.

I think this is the case. I ran ifconfig and this is the result:

ens3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 9000
        inet 10.0.0.230  netmask 255.255.255.0  broadcast 10.0.0.255

So I assume I should put 10.0.0.230:53 in the config but that was not explained anywhere in the readme or other places making it confusing to get started with acme-dns.