flyemoji
2810fe849c
RouteDNS ran `cloudflared tunnel route dns` without --overwrite-dns and swallowed the resulting "record already exists" error as success. When a hostname already had a CNAME from an earlier tunnel that was deleted and recreated, the record stayed bound to the dead tunnel: the setup reported the hostname "routed" while it kept returning Cloudflare error 1033 (the tunnel it pointed at has no connector). Pass --overwrite-dns so the record is repointed at the tunnel just created, making the route idempotent and correct on every re-run, and drop the now-unnecessary "already exists" swallow. INTEGRATION-ONLY (ExecRunner shells out to the real cloudflared binary).