docs: [#407] submit UDP1 tracker to newTrackon — complete

docs/deployments/hetzner-demo-tracker/README.md

@@ -42,7 +42,9 @@ Deploy a public Torrust Tracker demo instance to Hetzner Cloud and document ever
 8. [Observations](observations.md) — cross-cutting insights and learnings about the deployer
 9. [Maintenance](maintenance/README.md) — post-deployment operational tasks:
    - [Secrets rotation](maintenance/secrets-rotation.md) — rotate all secrets after AI-assisted deployment
-10. [Tracker Registry](tracker-registry.md) — submit the tracker to public registries (newTrackon)
+10. [Tracker Registry](tracker-registry.md) — submit the tracker to public registries (newTrackon):
+    - [newTrackon Prerequisites](post-provision/newtrackon-prerequisites.md) — BEP 34 DNS TXT records and
+      unique-IP policy required by newTrackon (needed to list the UDP1 tracker, see [issue #407](https://github.com/torrust/torrust-tracker-deployer/issues/407))
 11. [Bugs](bugs.md) — all deployer bugs discovered during this deployment (11 bugs, 1 fixed)
 12. [Improvements](improvements.md) — all improvement recommendations collected in one place (13 items)
 

docs/deployments/hetzner-demo-tracker/post-provision/README.md

@@ -13,6 +13,15 @@ on the server via SSH.
 | 2. Volume Setup    | [volume-setup.md](volume-setup.md)       | ✅ Done |
 | 3. Hetzner Backups | [hetzner-backups.md](hetzner-backups.md) | ✅ Done |
 
+## Post-Deployment Steps
+
+Steps performed after the tracker is running and during ongoing operations:
+
+| Step                        | Guide                                                      | Status  |
+| --------------------------- | ---------------------------------------------------------- | ------- |
+| 4. newTrackon Prerequisites | [newtrackon-prerequisites.md](newtrackon-prerequisites.md) | ✅ Done |
+| 5. IPv6 UDP Tracker Issue   | [ipv6-udp-tracker-issue.md](ipv6-udp-tracker-issue.md)     | ✅ Done |
+
 ## Why Before `configure`?
 
 - **DNS**: The `configure` command installs Caddy as a TLS reverse proxy. Caddy uses

docs/deployments/hetzner-demo-tracker/post-provision/dns-setup.md

@@ -184,20 +184,20 @@ in the Cloud Console are only accessible via the **Hetzner Cloud API** — the o
 
 ### Records to Create
 
-| Subdomain | Type | Value                   |
-| --------- | ---- | ----------------------- |
-| `http1`   | A    | `116.202.176.169`       |
-| `http1`   | AAAA | `2a01:4f8:1c0c:9aae::1` |
-| `http2`   | A    | `116.202.176.169`       |
-| `http2`   | AAAA | `2a01:4f8:1c0c:9aae::1` |
-| `api`     | A    | `116.202.176.169`       |
-| `api`     | AAAA | `2a01:4f8:1c0c:9aae::1` |
-| `grafana` | A    | `116.202.176.169`       |
-| `grafana` | AAAA | `2a01:4f8:1c0c:9aae::1` |
-| `udp1`    | A    | `116.202.176.169`       |
-| `udp1`    | AAAA | `2a01:4f8:1c0c:9aae::1` |
-| `udp2`    | A    | `116.202.176.169`       |
-| `udp2`    | AAAA | `2a01:4f8:1c0c:9aae::1` |
+| Subdomain | Type | Value                   | Notes                           |
+| --------- | ---- | ----------------------- | ------------------------------- |
+| `http1`   | A    | `116.202.176.169`       |                                 |
+| `http1`   | AAAA | `2a01:4f8:1c0c:9aae::1` |                                 |
+| `http2`   | A    | `116.202.176.169`       |                                 |
+| `http2`   | AAAA | `2a01:4f8:1c0c:9aae::1` |                                 |
+| `api`     | A    | `116.202.176.169`       |                                 |
+| `api`     | AAAA | `2a01:4f8:1c0c:9aae::1` |                                 |
+| `grafana` | A    | `116.202.176.169`       |                                 |
+| `grafana` | AAAA | `2a01:4f8:1c0c:9aae::1` |                                 |
+| `udp1`    | A    | `116.202.177.184`       | Updated 2026-03-06 (issue #407) |
+| `udp1`    | AAAA | `2a01:4f8:1c0c:828e::1` | Updated 2026-03-06 (issue #407) |
+| `udp2`    | A    | `116.202.176.169`       |                                 |
+| `udp2`    | AAAA | `2a01:4f8:1c0c:9aae::1` |                                 |
 
 ### API Approach
 
@@ -297,6 +297,28 @@ udp1: A=116.202.176.169  AAAA=2a01:4f8:1c0c:9aae::1
 udp2: A=116.202.176.169  AAAA=2a01:4f8:1c0c:9aae::1
 ```
 
+## Step 4: Update DNS Records for UDP1 (2026-03-06)
+
+As part of issue #407 (submitting the UDP1 tracker to newTrackon), the `udp1` A and AAAA records
+were updated to point to the new dedicated floating IPs:
+
+| Subdomain | Type | Old value               | New value               |
+| --------- | ---- | ----------------------- | ----------------------- |
+| `udp1`    | A    | `116.202.176.169`       | `116.202.177.184`       |
+| `udp1`    | AAAA | `2a01:4f8:1c0c:9aae::1` | `2a01:4f8:1c0c:828e::1` |
+
+Verified with `dig` (2026-03-06):
+
+```text
+$ dig A udp1.torrust-tracker-demo.com +short
+116.202.177.184
+
+$ dig AAAA udp1.torrust-tracker-demo.com +short
+2a01:4f8:1c0c:828e::1
+```
+
+✅ `udp1.torrust-tracker-demo.com` now resolves exclusively to the UDP1 floating IPs.
+
 ✅ All 12 records resolve correctly globally.
 
 > DNS propagation with Hetzner's nameservers (`helium.ns.hetzner.de`, `hydrogen.ns.hetzner.com`,
@@ -305,8 +327,11 @@ udp2: A=116.202.176.169  AAAA=2a01:4f8:1c0c:9aae::1
 
 ## Outcome
 
-✅ All subdomains resolve to `116.202.176.169` (A) and `2a01:4f8:1c0c:9aae::1` (AAAA). DNS
-setup is complete. The next step is [volume-setup.md](volume-setup.md).
+✅ All subdomains resolve correctly. After the 2026-03-06 update, `udp1.torrust-tracker-demo.com`
+resolves to the dedicated `udp1` floating IPs (`116.202.177.184` / `2a01:4f8:1c0c:828e::1`)
+while all other subdomains continue to resolve to `116.202.176.169` (A) and
+`2a01:4f8:1c0c:9aae::1` (AAAA). DNS setup is complete.
+The next step is [volume-setup.md](volume-setup.md).
 
 ## Problems