Run your subdomain on your own Cloudflare
Hand the whole subdomain to your own Cloudflare account and manage it there.
This is the best of both: you keep a memorable
name.ajaira.site, and everything about how it behaves —
proxying, caching, firewall rules, Workers, redirects — happens in your own Cloudflare
account, on your own dashboard.
How it works
DNS is a chain of referrals. We are authoritative for
ajaira.site, so when someone looks up your subdomain the
question reaches us. By publishing NS records for your name, we stop
answering it ourselves and instead say “ask these nameservers” — a
zone cut. From that point your Cloudflare account owns the name and everything
beneath it.
Step 1 — Add the subdomain as a site in Cloudflare
In your Cloudflare dashboard choose Add a site and enter the full
subdomain, e.g. myname.ajaira.site — not
ajaira.site, which is not yours to add.
Step 2 — Copy the two nameservers
Cloudflare shows you two, looking like
ana.ns.cloudflare.com and
rick.ns.cloudflare.com. They are specific to your account.
Step 3 — Add them here as NS records
| Type | Name | Value |
|---|---|---|
| NS | @ | ana.ns.cloudflare.com |
| NS | @ | rick.ns.cloudflare.com |
Add both. One nameserver is a single point of failure, and Cloudflare will not consider the zone active until it sees the pair.
Step 4 — Let it settle
Cloudflare rechecks periodically and flips the zone to Active, usually within minutes. Confirm the referral yourself:
dig NS myname.ajaira.site +shortWhen that prints your Cloudflare nameservers, the handover is done.
What changes for you
- Add and edit records in Cloudflare, not here. Our DNS manager stops being the source of truth for that name.
- Any records you already had here stop being served — the delegation replaces them. Recreate the ones you need in Cloudflare.
- You get Cloudflare's proxy, Universal SSL, WAF, page rules, Workers and analytics on your subdomain.
- Our record limit stops mattering: we hold two NS records, you hold as many as your Cloudflare plan allows.
Taking it back
Delete the NS records here and the name comes home — we answer for it again and the DNS manager works as before. Remove the site from Cloudflare too, or it will sit there showing an error.
Things worth knowing
- The subdomain is still ours to govern. Delegation does not transfer ownership. The Acceptable Use Policy applies to whatever you serve, and removing the NS records takes the whole thing offline instantly — which is exactly what we do if it is used for phishing or malware.
- Renewals still apply. A delegated subdomain expires on the same schedule as any other, and expiry deletes the NS records too. Sign in weekly.
- Email needs its own thought. MX records for the name now live in Cloudflare, not here.