This is what happened the morning after I moved off Notion.
You leave Notion. Rebuild everything. Astro. Pipeline. Deploy. It’s faster, cleaner, actually yours. You ship.
Then you send your page off to the world by sharing over Imessage, X and LinkedIn.
Feedback: “Same page buckarooo … try asking claude to vibe code it again”
That’s the DNS tax. You don’t skip it.
I thought the work was the rebuild. It wasn’t.
The real work starts when you replace one system with many. Notion was one surface. Now it’s DNS, Cloudflare, Pages, browsers, crawlers.
More control. More ways to be wrong.
Cloudflare makes it feel easy.
One table. Change a record. Done.
Except DNS doesn’t serve anything. It only points.
If the host doesn’t recognize the domain, nothing shows up. Not broken — just empty.
I deleted the old Notion CNAME, added what looked like the right replacement, and got a 522 error. Cloudflare reaching into its own network and timing out. A machine confused by itself. Forty minutes of refreshing a page I’d just broken.
The actual problem: DNS pointed at Cloudflare Pages, but Pages didn’t know the domain was mine. Two separate configs. Both had to be right. I’d only changed one.
That’s the trap. Everything looks right. Nothing works.
The rule is simple: DNS points. The host serves. Miss either and you’re offline. Half-right is the worst state.
While I was in that hole I convinced myself the next problem was the API. I wanted to stop touching the dashboard — manage DNS programmatically, pull records, make changes without clicking around a table and hoping.
Reasonable idea. I spent an hour on it. Reading docs, generating tokens, scoping permissions, hitting auth errors I couldn’t explain. Three different Stack Overflow threads from 2019, all contradicting each other.
The actual solution: stop. Open Claude Code. The Cloudflare MCP was sitting right there. I asked it to list the DNS records. Four seconds. Every call I’d been fumbling through manually — zones, records, Pages config, deployment logs — available as a conversation.
The hour on auth was entirely self-inflicted.
Then you fix it.
It works. You refresh.
Still Notion.
Now you’re not talking to your server. You’re talking to caches.
Browser. CDN edge. Apple link previews. Google Search Console.
Each one holding a different version of your site. Each on its own clock.
I shared the URL over iMessage — old Notion thumbnail. I opened Search Console — Notion favicon next to my domain, black N, like I’d never left. There is no endpoint to call, no cache-control header that reaches Apple’s servers, no support ticket that moves Google’s index faster.
You submit your sitemap. You click “Request Indexing.” Then you wait. Days. Maybe a week.
There’s no fix. You can request. You can hint. Mostly, you wait.
The mistake wasn’t DNS.
It was thinking I was in control.
Notion hides the system. One surface, one vendor, one set of problems you don’t have to think about. When you leave, you inherit the system you didn’t know was there.
And it doesn’t move when you do.
You can deploy instantly.
You can’t propagate instantly.
The rewrite was the work. The rewrite took weeks.
The DNS tax took an afternoon and it’s still not fully paid — somewhere in Apple’s infrastructure there’s a cached preview of a page that doesn’t exist anymore.
The work is learning where control ends.
Pay the tax.
It clears when it clears.