Ah, I see the probable cause of the problem.
You’ve ping’ed the api.[mydomain].org and it should return a IP address, but it couldn’t resolve the host. This means it’s a DNS problem. It can’t reach the server because it doesn’t know which server to talk to.
And after the dig commands, the problem is definitely your DNS. You’ve set the following DNS:
api.[mydomain.org] IN CNAME api.[mydomain].org
The CNAME record is just something like: For this domain (api.[mydomain].org), use the same DNS configuration as the value IP (in this case also api.[mydomain].org. So it’s pointing to itself, which stays in a constant loop.
What I like to do when setting up openBalena, is creating a subdomain like:
balena.[mydomain].org
And setting all my A (IPv4 of the server) and AAAA (IPv6 of the server) records to that subdomain. Setting up openBalena with that domain, so:
./scripts/quickstart -U <super_username> -P <super_user_password> -d balena.[mydomain].org
And setting the DNS CNAME’s like this:
api.balena.[mydomain].org IN CNAME balena.[mydomain].org
registry.balena.[mydomain].com IN CNAME balena.[mydomain].org
vpn.balena.[mydomain].com IN CNAME balena.[mydomain].org
s3.balena.[mydomain].com IN CNAME balena.[mydomain].org
You’re probably ready to set-up your devices now!
Also, it could take up to 72 hours for DNS changes to take effect. This is almost never the case and depends on what you’ve set-up in your DNS, but it could take a while.