chore(dns): retire the sean.pm zone from the platform #727
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/retire-seanpm-zone"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hermes was the only thing served at
sean.pm, and it is gone. This drops thezone from the ExternalDNS domain filter and from the ACME issuer solver, and
removes the two guard lines in
tests/dns-domain-contract.shthat pinned both.ExternalDNS never managed those records
It runs
--registry=txt, and theseanpmzone has no ownership TXT record.So the
AandAAAArecords are manual, which is why they outlived theHTTPRoute that
--policy=syncwould otherwise have withdrawn them with. Theystill point at the portal gateway LoadBalancer, which no longer has a
sean.pmlistener, so the name resolves and then fails TLS.
Removing those two records is a Cloud DNS change, not a GitOps one, and is not
part of this commit:
The managed zone stays
sean.pmis a domain the platform hosted a service for, not a domain theplatform owns. The zone carries its NS delegation, and deleting it would
decommission the domain rather than clean up after Hermes.
bash tests/dns-domain-contract.shpasses:"DNS has six objects, stable zones and owner ID, and one pruning Flux owner".
https://claude.ai/code/session_01GfkEuwuvGSqGyXVuxwT7PA