If you manage websites, chances are you’ve run into the question of where your DNS should live. Things get especially interesting when you’re using multiple services — for example, Cloudflare as your registrar and DNS manager, and Amazon AWS Route 53 for specific integrations like ServerAvatar white label setup.
Recently, I set up temporary domains and file manager domains for a ServerAvatar panel, and the process required using Route 53. Instead of moving all my domains away from Cloudflare (which I like for security, caching, and simplicity), I went with NS delegation — pointing only a subdomain to Route 53 while keeping Cloudflare in charge of the main domain.
Here’s how it works.
Why Mix Cloudflare and Route 53?
- Cloudflare: Handles domain registration, global CDN, DDoS protection, and simple DNS management.
- Amazon Route 53: Needed by ServerAvatar to manage certain white label and temporary domains. It expects to control the zone directly.
- ServerAvatar: Provides automated server management, app installs, backups, and white label client panels.
By delegating a subdomain (like temp.mydomain.com) to Route 53, you get the best of both: Cloudflare stays in charge of the main domain, but Route 53 gets authority where it’s required.
Key Concept: NS Delegation
NS records (Name Server records) tell the internet which nameservers are authoritative for a domain or subdomain. Instead of moving your entire domain from Cloudflare to AWS, you can:
- Create a new hosted zone in Route 53 for the subdomain.
- Copy the NS records AWS gives you.
- Add those NS records to your main domain’s DNS in Cloudflare.
This tells the internet: “For temp.mydomain.com, go ask Route 53.”
Step-by-Step Setup
1. Create a Hosted Zone in AWS
- Log in to Route 53.
- Create a new hosted zone for your subdomain (temp.greencha.cc).
- AWS will give you a set of NS records.
2. Add NS Records in Cloudflare
- Log in to Cloudflare and open your domain (greencha.cc).
- Add NS records for temp pointing to the four Route 53 nameservers provided.
- Save the changes.
3. Wait for Propagation
DNS changes can take anywhere from a few minutes to 24 hours. Use tools like dig, nslookup, or online DNS checkers to confirm the delegation is working.
4. Connect in ServerAvatar
- In your ServerAvatar white label panel, enter the delegated domain (e.g., temp.greencha.cc).
- ServerAvatar will validate it against Route 53.
- Once accepted, you can start creating temporary or staging applications under that subdomain.
Common Issues
- Recently registered domains: Some registrars (like Cloudflare) have a 60-day lock before you can move nameservers. Delegation via NS records avoids this problem.
- Forgetting delegation vs full transfer: Only add NS records for the subdomain in Cloudflare — don’t change your main domain’s nameservers unless you want to move everything.
- SSL certificates: If you use staging or temporary domains, you may need to configure Let’s Encrypt or another SSL provider in ServerAvatar.
Lessons Learned
- Keep your main domain’s DNS in Cloudflare if you like its features.
- Use Route 53 only where it’s required, such as with ServerAvatar integrations.
- Plan your subdomain names carefully — temp, staging, or site are common options.
- Even though DNS feels complicated, NS delegation is a clean way to balance multiple providers.
Conclusion
By combining Cloudflare and Amazon AWS Route 53 through NS delegation, I was able to set up ServerAvatar white label temporary domains without giving up my preferred DNS setup. This approach gives flexibility, keeps management simple, and supports growth when hosting multiple client projects.
If you’re juggling domains across services, consider delegation instead of full migration. It’s a small adjustment that makes a big difference.