Ability to use other programmable dns instead of uncloud.dns

[airtonix]

Wondering how intertwined uncloud is with https://docs.uncloud.run/#managed-dns-service.

can we change our configuration to point at our own programmable dns server? something like our own CoreDns server or even Cloudflare?

Perhaps you can enable it via custom clients that teach uncloud how to communicate and work with other dns soltions?

[psviderski]

I answered a similar question about the managed DNS a few days ago: #85 (comment). Will copy and extend the reply:

The Managed DNS service providing *.cluster.uncloud.run domains is optional. It's enabled by default but you can disable it when initialising your first machine uc machine init --no-dns. Also, you can reserve or release this record at any time with the following commands:

uc dns reserve
uc dns release

When you don't use this DNS service, you can manually manage your domain records, e.g. create A records pointing to your servers' public IPs through your DNS provider (Cloudflare, Namecheap, etc.).

This feature was added to provide a nice UX to new users who may not have their own DNS domain yet but would like to try out self-hosting with proper domain names and HTTPS. Also, when you add more machines to the cluster or change the deployment of the reverse proxy (Caddy), this cluster record is automatically updated to point to the public IP addresses of the machines running Caddy. So it could be a bit more convenient to use it to not manually manage IP addresses for your own domain, but just create a CNAME instead. Please see https://docs.uncloud.run/getting-started/deploy-demo-app#use-your-own-domain for details.

can we change our configuration to point at our own programmable dns server? something like our own CoreDns server or even Cloudflare?

You can run the Managed DNS component on your own: https://github.com/psviderski/uncloud-dns
You can provide the endpoint to it when initialising the machine uc machine init --dns-endpoint https://... or when reserving a cluster domain uc dns reserve --endpoint https://....

This is the only API currently supported. I believe you can disable this feature and script some automation on your own if you want to automatically update your DNS records when you add new machines to the cluster or change the machines on which the reverse proxy runs. If your machines are fairly static, you shouldn't really need this.

Note also that the uncloudd daemon running on each machine embeds a tiny DNS server that resolves the addresses of other services running in the cluster by their names (service-name.internal or just service-name) in a similar way Docker does on a single host.

Perhaps I should explicitly point out the Managed DNS is optional in the docs. Do you think it brings more confusion than it helps?

[matiasgarciaisaia]

I've submitted #93 before reading this discussion