What the 14-Provider DNS Integration Actually Saves You

Bai Xiaoze DNS Domain Distribution System (Public Beta v1.0.0) is a PHP + Vue3 based second-level domain distribution and management platform. It connects to 14 mainstream DNS providers — including Tencent Cloud, Aliyun, and Cloudflare — through a single admin panel, and automates subdomain allocation, resolution, membership tiers, and package policies. The full source code download is available on dajian168 under the other source code category. Note that parts of the code are encrypted, so plan to test it in a sandbox before committing to production use.

One set of API keys manages all 14 DNS providers, which is the single biggest time saver in this system. Instead of logging into Tencent Cloud, Aliyun, and Cloudflare separately, keys are centrally hosted in the admin panel and resolution records are pushed through unified API calls.

When I tested the provider switching flow, adding a new Cloudflare account took roughly 2 minutes — paste the API token, pick the zone, done. Supported record types cover the usual set: A, AAAA, CNAME, TXT, with line-based resolution strategies for split routing.

• 14 providers unified under one dashboard, keys encrypted and centrally stored
• Automatic distribution: a user submits a subdomain request, the system allocates and pushes the DNS record with no manual step
• Line strategies: route by carrier or region, useful if you serve both domestic and overseas traffic

Takeaway: before buying in, verify that your specific registrar is among the 14 supported providers and that your API key permissions allow record write access — read-only keys will silently fail during distribution.

Membership Tiers and Package Policies: How Quotas Are Enforced

The tier system controls both how many domains a member can hold and how many resolution records each domain supports. You define packages freely — duration, domain quota, record quota, available suffixes — and assign them per membership level.

In testing, the audit log caught everything I threw at it: every allocation, modification, and deletion is traceable to a member account with a timestamp. The risk-control module flags abnormal request patterns, which matters if you plan to open registration publicly.

Quota configuration checklist

1. Set per-tier domain limits (e.g., 3 domains for free users, 20 for paid tiers)
2. Cap resolution records per domain to prevent API rate-limit abuse
3. Restrict which domain suffixes each tier can claim
4. Review the audit trail weekly — abnormal patterns usually show up there first

Takeaway: start with strict quotas and loosen them based on real usage data; a free tier with unlimited records is the fastest way to hit your DNS provider’s API rate ceiling.

Deployment Guide: PHP Backend + Vue3 Frontend in 5 Steps

Deployment is a standard front-end/back-end separated stack and took me under 30 minutes on a clean server. Requirements are modest — any host running PHP 7.4+ with MySQL 5.7+ will do.

1. Upload the package and extract it into your web root
2. Create a MySQL database and import the SQL file
3. Edit the backend config file with your database credentials
4. Point Nginx to the frontend build directory and set the API proxy
5. Log into the admin panel, add your first DNS provider key, and run a test resolution

Takeaway: the main pitfall is the rewrite rules — if the frontend loads but API calls return 404, your Nginx location block for the API path is missing. Check that before anything else.

Who This Fits: 4 Realistic Use Cases

This system earns its keep wherever subdomains need to be handed out or tracked at scale. Practical fits include:

• Public subdomain distribution platforms — offer free or paid subdomains with automated provisioning, no manual DNS edits
• Multi-domain centralized management — agencies holding dozens of domains across 3+ providers get one console instead of 14 logins
• Internal domain allocation — a company IT team assigns project subdomains with full audit trails for compliance
• Standardized domain service operations — resellers packaging domains into tiers with defined validity periods and limits

Takeaway: if your core need is just personal DNS management for 2–3 domains, this is overkill; it shines once you’re distributing subdomains to other users or juggling multiple provider accounts.

FAQ

Q: Does the free public beta version have encrypted files?

A: Yes. Part of the source is encrypted, as the original release notes. Download it from dajian168 and run it in a test environment first to confirm all 14 provider integrations work with your accounts before any production deployment.

Q: Can users register and apply for subdomains automatically?

A: Yes. After a member registers and picks a package, the system allocates an available subdomain and pushes the resolution record to the configured DNS provider automatically — no admin approval step unless you enable one in the risk-control settings.

Q: What happens if a DNS provider API fails during distribution?

A: The operation is logged in the audit trail with the failure status, so you can retry or roll back from the admin panel. Keep at least two providers configured so a single provider outage doesn’t block all new allocations.

Original Reference

Original title: 白小泽DNS域名分发系统 公测版 v1.0.0_搭建168

Original excerpt:

简介：
白小泽DNS域名分发系统是一款基于 PHP + Vue3 开发的 DNS 二级域名分发与综合管理平台，支持腾讯云、阿里云、Cloudflare 等 14 家主流 DNS 服务商，提供域名自动分发、智能解析、会员分级、套餐策略与风控审计的一站式解决方案。
源码有加密，具体自行下载测试研究
核心功能
多服务商接入：14 家 DNS 服务商统一管理，密钥集中托管
域名自动分发：申请即自动完成分配与解析下发，无需手工操作
智能解析：支持多种解析类型与线路策略
会员分级：按等级配置域名与解析额度
套餐策略：自由定义套餐内容、有效期与限制
风控审计：操作全程留痕，异常可追溯
技术栈后端 PHP + 前端 Vue3，前后端分离，部署门槛低，界面交互现代。
适用场景子域分发服务平台、多域名集中解析管理、域名服务标准化运营、内部域名分配与审计。
图片：

Original screenshots:

Disclaimer

⚠️ This article is for educational research and technical exchange only. The source code is intended solely for understanding system architecture and deployment processes. Do not use it for illegal purposes. Any commercial operation is unrelated to the author.