DNS held hostage: when your old host keeps serving your domain after you cancel

How DNS gets held hostage

Three layers have to agree on where your domain lives:

1. Registrar (where you buy the domain) publishes which nameservers are authoritative.
2. Authoritative nameservers (often provided by your host) answer "here are the A / MX / TXT records".
3. Resolvers (Google 8.8.8.8, Cloudflare 1.1.1.1, your ISP) cache those answers for the record's TTL.

When you signed up at Bluehost or GoDaddy, the onboarding wizard either (a) set your registrar's nameservers to the host's NS, or (b) registered the domain for you and automatically pointed NS at their DNS. If you never changed that, the old host remains layer 2 — the authoritative answer-giver — even after you stop paying for hosting.

Some hosts respond to cancellation by:

• Parking the domain — returning A records to a "This site is unavailable" page.
• Returning SERVFAIL or NXDOMAIN — so email bounces and the site looks dead.
• Serving stale records — your old IP answers, but nothing is listening.
• Holding the zone in limbo for 7–30 days while "deprovisioning" runs.

Diagnose: whose NS is actually answering

Run these four checks in order. You need the exact output of each before you pick a fix.

1. Who does the registrar say is authoritative?

Run whois yourdomain.com | grep -i "name server" (or use our free WHOIS checker). You will see 2–4 NS hostnames. If they look like ns1.bluehost.com, dns1.registrar-servers.com, ns.inmotionhosting.com, etc., your old host is still authoritative.

2. What do those NS actually answer?

dig @ns1.bluehost.com yourdomain.com A +short — this bypasses caching and asks the host's NS directly. If it returns an IP you do not recognise, or a parking IP (often a /24 the host uses for "suspended" sites), you have proof the old host is still answering.

3. What are resolvers serving right now?

dig @8.8.8.8 yourdomain.com A +short and dig @1.1.1.1 yourdomain.com A +short. If these differ from step 2, caching is masking the problem — it will flip to the old host's answer when TTL expires.

4. Is the domain itself still registered to you?

In the WHOIS output, confirm the registrant email is yours and expiration is not past. If expiration is past, the registrar has likely redirected to a parking portal regardless of hosting — that is a different problem (see our redemption-fee guide).

Force a clean cut-over in 15 minutes

Once you know the old host's NS is the problem, the fix is to replace them with nameservers you control. You do not need to transfer the domain away from the registrar for this.

1. Pick new authoritative DNS. Free options: Cloudflare (fastest, most reliable), deSEC, Hetzner DNS Console. Paid, independent: DNSimple, DNS Made Easy. Or point at your new host's NS (ours: ns1.launchpadhost.com, ns2.launchpadhost.com).
2. Build the zone before you flip. Create A / AAAA / MX / TXT / CNAME records matching what is live now. Verify against dig @new-ns yourdomain.com.
3. Lower TTLs 48 hours in advance if possible — drop from 14,400s to 300s. Then flip. If you cannot lower TTLs (because the old NS refuses to publish changes), accept a 4-hour propagation window.
4. Update NS at the registrar. Log in (Namecheap, Porkbun, GoDaddy's registrar panel, etc.), replace the old NS hostnames with the new ones, save. The registry updates within minutes; global propagation typically completes in 1–4 hours.
5. Verify. Use our DNS propagation checker to watch 20+ resolvers worldwide flip to the new answers. Once all resolvers show the new IP, the old host can return NXDOMAIN all day — nobody is asking them any more.

Documented cases

Bluehost cancellation → parking page. Multiple r/webhosting threads (including one in Feb 2024 titled "Bluehost is holding my DNS hostage") report that after account closure, Bluehost's NS continues answering with a 1 Bluehost-branded parking IP for up to 30 days unless the customer explicitly changes NS at the registrar first.

GoDaddy hosting cancellation → MX reset. GoDaddy's automated deprovisioning drops MX records back to a default when hosting ends, even if the domain stays registered there. Email stops flowing until the customer manually re-enters MX in GoDaddy's DNS Manager or flips NS to a different provider. Documented on Web Hosting Talk thread #1878433 and GoDaddy's own community forum.

Network Solutions "DNS retention fee". NetSol has historically offered a paid "DNS hosting" SKU separate from domain registration. Customers who cancel shared hosting but keep the domain registered are sometimes auto-enrolled at $14.99/yr for the DNS that was previously bundled — if they refuse to pay, the zone stops resolving. Confirmed in BBB complaints filed 2023–2025.

The common thread: if you never moved NS away from the host, you are one cancellation away from a dead website.

How LaunchPad Host handles customers who leave

We operate on a simple rule: your domain is yours. Our DNS is a courtesy, not a lock.

• When you cancel hosting, your DNS zone remains live and served by our NS for 30 additional days at no charge — enough time for you to build a new zone elsewhere and flip NS at your leisure.
• If you need the zonefile, we export it as a standard BIND-format file on request. Import it into Cloudflare, Route 53, or any other provider in one upload.
• We never park cancelled domains. A cancelled site stops serving HTTP; DNS keeps answering truthfully until you move it.
• No "DNS retention fee" invoice. Ever.

This is part of the same philosophy behind our transparent renewal pricing and free WHOIS privacy: we make money by being useful, not by making it expensive to leave.