How to connect athio.ai, align360.io, and any future domain to NowPage — with every 2nd-order effect mapped
DNS confusion comes from conflating three separate systems. Here's what each one does.
Where you bought the domain (GoDaddy, Namecheap). Controls nameservers — who answers "where does athio.ai live?" This is the ONLY thing that matters at the registrar level.
Manages DNS records (A, CNAME, MX). Could be the registrar itself, Hostinger, or Cloudflare (recommended). Whoever the nameservers point to IS your DNS provider.
Where your files/apps live (Hostinger, Vercel). Changing DNS does NOT delete files on Hostinger. You always access Hostinger via hpanel.hostinger.com — that's login-based, not domain-based.
| Domain | Registrar | Current DNS | Current Hosting | Status |
|---|---|---|---|---|
| ideas.asapai.net | - | Cloudflare | Vercel (NowPage) | Working |
| athio.ai | GoDaddy | Hostinger | Hostinger | Pending |
| align360.io | Namecheap | Hostinger | Hostinger | Pending |
Before changing DNS, figure out what you'll lose (if anything).
You can keep it on a subdomain:old.athio.ai or legacy.athio.ai
Safe to point the whole domain to Vercel. Hostinger hosting stays intact but just won't be reachable via the domain.
You MUST add MX records in Cloudflare pointing to Hostinger's mail servers.
No MX records needed. Clean setup.
Use the same Cloudflare account that manages asapai.net.
Enter athio.ai and select the Free plan.
They'll look something like:
Write these down or keep the tab open. You'll need them in the next phase.
Before changing nameservers, add these records in Cloudflare's DNS tab:
The wildcard * record is critical — it means any subdomain you create in the NowPage dashboard (design.athio.ai, blog.athio.ai, etc.) will automatically resolve. Without it, each subdomain needs a separate DNS record.
Set proxy status to DNS only (grey cloud) or Proxied (orange cloud) — both work. Proxied gives you Cloudflare's CDN + DDoS protection.
Check Hostinger's current MX records and replicate them in Cloudflare. Typical Hostinger MX:
Skip this if you don't use email on athio.ai.
Scroll down to Nameservers. Click "Change" or the edit icon. They'll currently show Hostinger's nameservers (like ns1.dns-parking.com or ns1.hostinger.com).
Choose "I'll use my own nameservers" or "Custom". Enter the two Cloudflare nameservers from Step 3:
Click Save.
Go back to Cloudflare. It may take a few minutes to detect the nameserver change. Once it does, athio.ai will show as "Active" in your Cloudflare dashboard.
Go to the NowPage dashboard and click "Verify DNS" for athio.ai. If using grey cloud (DNS only), it should turn green. If using orange cloud (proxied), it may stay "Pending" — but the domain will work.
Add align360.io to Cloudflare (same account). Add the same DNS records:
The wildcard record enables all future subdomains (design.align360.io, blog.align360.io, etc.) without needing separate DNS entries for each one.
Cloudflare will give you a different pair of nameservers for this domain. Note them down.
Under the "Nameservers" dropdown, change from "Namecheap BasicDNS" (or "Custom DNS" pointing to Hostinger) to "Custom DNS".
Enter Cloudflare's nameservers for align360.io:
Click the green checkmark to save.
Same as athio.ai — wait 1-4 hours, confirm Active in Cloudflare, then Verify DNS in NowPage.
Everything that changes (and doesn't) when you switch nameservers to Cloudflare.
Your Hostinger hosting is completely independent of DNS. Nothing gets deleted.
Always accessible at hpanel.hostinger.com with your login credentials. DNS changes don't affect this.
All files remain on Hostinger's servers. Access via File Manager in hPanel or FTP using Hostinger's server IP (not the domain name).
Works as long as MX records point to Hostinger's mail servers. Set these up in Cloudflare before changing nameservers.
MySQL/MariaDB databases on Hostinger are untouched. Access them through phpMyAdmin in hPanel or via the server IP.
The same pattern works for every domain, regardless of registrar.
A @ → 76.76.21.21, CNAME www → cname.vercel-dns.com, and CNAME * → cname.vercel-dns.com (wildcard for subdomains)If your nameservers point to Hostinger, Hostinger's DNS should work. But Hostinger sometimes has conflicts between their hosting setup and custom DNS records. They may override or ignore records that conflict with their hosting configuration. Cloudflare eliminates this by being a pure DNS provider with no hosting opinions.
NowPage handles this automatically when you add a domain in the dashboard. The domain gets registered with the Vercel project. You just need DNS pointing to Vercel's IP.
If you added the wildcard CNAME * → cname.vercel-dns.com record (recommended), all subdomains will resolve automatically. Just create the subdomain in the NowPage dashboard — it's instant. No extra DNS records needed per subdomain.
If you didn't add the wildcard, you'll need a separate CNAME for each subdomain (e.g., CNAME design → cname.vercel-dns.com).
Yes. Just change the nameservers back to Hostinger's at your registrar. Everything reverts within 1-48 hours. Or keep Cloudflare and just change the A record to point to Hostinger's IP instead of Vercel's.
Because it uses Cloudflare's proxy (orange cloud). NowPage's DNS verifier does a lookup and sees Cloudflare's IP (104.x.x.x) instead of Vercel's (76.76.21.21). The page works fine — the status is a cosmetic false-negative in our dashboard.
Not yet. Keep it active until you've confirmed everything works on NowPage and you've migrated anything you need. Once you're sure there's nothing on Hostinger you need, you can let the hosting expire. The domain registration (at GoDaddy/Namecheap) stays separate — don't confuse hosting renewal with domain renewal.