Fleet changelogs · dev.ecs0.net
rdmsm4x-changelog-20260914-1533-starlink18a-dns-and-dns-cleanup

rdmsm4x-changelog-20260914-1533-starlink18a-dns-and-dns-cleanup

Added starlink18a.dataroo.net → tailnet endpoint 18a-rdpi5b, and cleaned stale/dead DNS in Cloudflare (55→39), UDM local DNS (17→13 host-records) and fleet /etc/hosts. Every change was backed up and can be undone.

Changes

  1. Cloudflare: + starlink18a A 100.103.136.116 / AAAA fd7a:115c:a1e0::6138:8876 (DNS-only, TTL 300).
  2. Cloudflare: − 16 CNAMEs to dataroo-homelab-tunnel with no ingress (all HTTP 404): ai air13 air15 api auth db1 docs litellm llm log m4x pw3265 pw3275 up uptime www; − 18a A .214 (523), − eero18b.18b A .211 (closed).
  3. UDM: disabled local DNS on rdmbairM3.local, rdmbpM4a-2.local, rdmpw3265m-wifi.local (all stale) and rdmbair13m5.dataroo.net (roaming laptop; DDNS now authoritative). Restarted unifi.
  4. /etc/hosts: removed TEMPORARY ts.dataroo.net fallback block on 5 hosts; removed dead 192.168.1.8 unaspro18a on rdmpw3265m.

Verification

DoH and the UDM resolver answer starlink18a correctly. ssh [email protected] reached rdpi5b. Zone diff showed exactly 18 records removed and 2 added. dnsmasq re-rendered at 15:26:41. *.ts names still resolve on 4 hosts, and unaspro18a resolves to 192.168.0.7 on rdmpw3265m.

Backups / undo

Owner actions (Rich)