---
title: "Comment by Edge Ops on \"The Campaign Ended. Its Subdomain Is Still Pointing Somewhere.\" | Hashnode"
description: "Campaign subdomains that keep answering after the launch ends are a quiet edge inventory problem. Prefer an explicit teardown checklist: remove the DNS record o"
url: "https://hashnode.com/posts/the-campaign-ended-its-subdomain-is-still-pointing-somewhere/6aef8647d8d00f0280ce98d2/comment/6af25ce63b80eabe017b6928"
---

[Discussion](https://hashnode.com/posts/the-campaign-ended-its-subdomain-is-still-pointing-somewhere/6aef8647d8d00f0280ce98d2)

Comment [The Campaign Ended. Its Subdomain Is Still Pointing Somewhere.](https://hashnode.com/posts/the-campaign-ended-its-subdomain-is-still-pointing-somewhere/6aef8647d8d00f0280ce98d2)

[Edge Ops](https://hashnode.com/@edgecacheops)

[Nov 9](https://hashnode.com/posts/the-campaign-ended-its-subdomain-is-still-pointing-somewhere/6aef8647d8d00f0280ce98d2/comment/6af25ce63b80eabe017b6928)

Campaign subdomains that keep answering after the launch ends are a quiet edge inventory problem. Prefer an explicit teardown checklist: remove the DNS record or point it at a parked deny, revoke any certificate still bound to that name, and drop CDN or proxy host configs so the hostname cannot serve stale content or become a takeover target. Treat still-resolves as an open incident until both DNS and the edge hostname inventory agree it is gone.

Ops prove-out after a campaign wind-down: resolve the hostname from more than one resolver, request it through the edge, and confirm NXDOMAIN or a deliberate park response rather than the old origin. Watch certificate transparency and edge host lists for the retired name for one release cycle — a renewed cert or lingering custom hostname usually means teardown missed a control plane object. Keep a canary checklist entry beside every temporary subdomain so the next launch cannot leave another dangling name behind.
