Managing DNS records across multiple domains can quickly become repetitive and error-prone — especially if you're handling dozens or even hundreds of zones.
Instead of adding records one by one, I built a way to bulk add DNS records across multiple Cloudflare zones in a single operation using Aioflare.
In this guide, I’ll show you exactly how it works.
🚀 The Problem
If you’ve ever had to:
- Add the same A record to 50+ domains
- Set up verification records across multiple zones
- Update IP addresses across many DNS entries
You already know:
This is slow, repetitive, and easy to mess up.
🎥 Video Tutorial
Watch how it works step-by-step:
🧩 Step-by-Step: Bulk Add DNS Records
1. Select Your Target Zones
Choose multiple zones where you want to apply DNS records.
You can filter by:
- Account
- Collection
- Record type or content
2. Define DNS Records
Create one or more DNS records to apply across all selected zones.
Example:
- Type:
A - Name:
@ - Content:
192.0.2.1
Or:
- Type:
CNAME - Name:
www - Content:
example.com
3. Use Dynamic Placeholders
You can use dynamic placeholders like:
{{zone}}
This will automatically be replaced with the actual domain name.
Example:
- Name:
verify-{{zone}} - Content:
some-token
👉 This is extremely useful for:
- Domain verification
- Automation workflows
- Scaling configurations
4. Execute the Bulk Operation
Click apply and the system will:
- Queue the job
- Process it server-side
- Continue even if your browser is closed
5. Check Results in Queue History
After execution, you can:
- View detailed results
- See which records succeeded or failed
- Open encrypted result logs
⚙️ How It Works Behind the Scenes
Bulk operations in Aioflare are designed for reliability and scale:
- Server-side queue processing (Cloudflare Workers)
- Retry-safe execution
- Encrypted result storage (R2)
- Handles large-scale operations without blocking UI
This means you can safely run operations across many zones without worrying about browser crashes or interruptions.
💡 Pro Tips
- Use record templates for repeated setups
- Combine with zone profiles for one-click deployment
- Organize zones using collections
- Use filters to target specific domain groups
🎯 Why This Matters
Instead of clicking through endless DNS forms, you can:
Apply changes across dozens (or hundreds) of domains in seconds.
If you're managing infrastructure, client domains, or large-scale projects — this is a huge time saver.
🧪 Join the Closed Beta
Aioflare is currently in private beta and I’m looking for early users who manage multiple Cloudflare zones.
👉 Join here:
https://tally.so/r/Pd9EAQ
💬 Feedback
If you have suggestions, feature requests, or run into issues — I’d love to hear from you.
What’s your biggest pain when managing DNS at scale?
Top comments (0)