docs: replace managed DNS domain: cluster.uncloud.run -> uncld.dev

website/docs/1-overview.md

@@ -69,7 +69,7 @@ Talos [KubeSpan](https://www.talos.dev/v1.10/talos-guides/network/kubespan/).
 
 ### Managed DNS service (optional)
 
-Uncloud can provide **managed DNS records** like `<service-name>.<cluster-id>.cluster.uncloud.run` for your public
+Uncloud can provide **managed DNS records** like `<service-name>.<cluster-id>.uncld.dev` for your public
 services through free [Uncloud DNS](https://github.com/psviderski/uncloud-dns) service. You can deploy a service and
 instantly access it from anywhere with a proper DNS name and HTTPS without any manual DNS configuration. This makes
 self-hosting much more accessible and simplifies the process of adding your own domain later.

website/docs/2-getting-started/2-deploy-demo-app.md

@@ -45,7 +45,7 @@ This command will:
 - Install the Uncloud daemon on your server
 - Create a Docker network for Uncloud-managed containers
 - Deploy [Caddy](https://caddyserver.com/) as your reverse proxy listening on host ports 80 and 443
-- Reserve a free `xxxxxx.cluster.uncloud.run` subdomain via the Uncloud managed DNS service and point it to your
+- Reserve a free `xxxxxx.uncld.dev` subdomain via the Uncloud managed DNS service and point it to your
   server's IP
 
 All in about a minute!
@@ -144,7 +144,7 @@ Cluster initialised with machine 'machine-dc3c' and saved as context 'default' i
 Current cluster context is now 'default'.
 Waiting for the machine to be ready...
 
-Reserved cluster domain: 7za6s7.cluster.uncloud.run
+Reserved cluster domain: 7za6s7.uncld.dev
 [+] Deploying service caddy 7/2
  ✔ Container caddy-d7uk on machine-dc3c     Started                                            6.1s
    ✔ Image caddy:2.10.0 on machine-dc3c       Pulled                                           3.7s
@@ -154,7 +154,7 @@ Updating cluster domain records in Uncloud DNS to point to machines running cadd
  ✔ Machine machine-dc3c (157.180.72.195)  Reachable                                            0.7s
 
 DNS records updated to use only the internet-reachable machines running caddy service:
-  *.7za6s7.cluster.uncloud.run  A → 157.180.72.195
+  *.7za6s7.uncld.dev  A → 157.180.72.195
 ```
 
 </details>
@@ -177,7 +177,7 @@ You'll see the progress of the deployment and the public URL where you can acces
    ✔ Image excalidraw/excalidraw on machine-dc3c  Pulled                    4.7s
 
 excalidraw endpoints:
- • https://excalidraw.7za6s7.cluster.uncloud.run → :80
+ • https://excalidraw.7za6s7.uncld.dev → :80
 ```
 
 ## Verify your deployment
@@ -209,7 +209,7 @@ uc ls
 ```
 NAME         MODE         REPLICAS   ENDPOINTS
 caddy        global       1
-excalidraw   replicated   1          https://excalidraw.7za6s7.cluster.uncloud.run → :80
+excalidraw   replicated   1          https://excalidraw.7za6s7.uncld.dev → :80
 ```
 
 You can see `caddy` service listed here. That's your reverse proxy, running as a regular Uncloud service.
@@ -266,15 +266,15 @@ We've successfully converted our deployment created with `uc run` to a Compose f
 
 ## Use your own domain
 
-Want to use your own domain, for example, `excalidraw.example.com` instead of `excalidraw.7za6s7.cluster.uncloud.run`?
+Want to use your own domain, for example, `excalidraw.example.com` instead of `excalidraw.7za6s7.uncld.dev`?
 
 Add a CNAME record `excalidraw.example.com` in your DNS provider (Cloudflare, Namecheap, etc.) pointing to
-`excalidraw.7za6s7.cluster.uncloud.run`. Alternatively, you can add an A record pointing to your server's IP.
+`excalidraw.7za6s7.uncld.dev`. Alternatively, you can add an A record pointing to your server's IP.
 
 :::info note
 
 These instructions set up your own domain **in addition to** the Uncloud managed DNS name
-`excalidraw.7za6s7.cluster.uncloud.run`.
+`excalidraw.7za6s7.uncld.dev`.
 
 If you want to avoid the managed service altogether, add `--no-dns` to your `uc machine init` command, and point an A
 DNS record to your server(s)'s IP(s).

website/docs/9-cli-reference/uc_dns.md

@@ -5,7 +5,7 @@ Manage cluster domain in Uncloud DNS.
 ## Synopsis
 
 Manage cluster domain in Uncloud DNS.
-DNS commands allow you to reserve or release a unique '\<id>.cluster.uncloud.run' domain for your cluster. When reserved, Caddy service deployments will automatically update DNS records to route traffic to the services in the cluster.
+DNS commands allow you to reserve or release a unique 'xxxxxx.uncld.dev' domain for your cluster. When reserved, Caddy service deployments will automatically update DNS records to route traffic to the services in the cluster.
 
 ## Options
 

website/docs/9-cli-reference/uc_machine_init.md

@@ -27,7 +27,7 @@ uc machine init [USER@HOST:PORT] [flags]
   # Initialise with a non-root user and custom SSH port and key.
   uc machine init ubuntu@<your-server-ip>:2222 -i ~/.ssh/mykey
 
-  # Initialise without Caddy (no reverse proxy) and without an automatically managed domain name (xxxxxx.cluster.uncloud.run).
+  # Initialise without Caddy (no reverse proxy) and without an automatically managed domain name (xxxxxx.uncld.dev).
   # You can deploy Caddy with 'uc caddy deploy' and reserve a domain with 'uc dns reserve' later.
   uc machine init root@<your-server-ip> --no-caddy --no-dns
 ```