Why You Need a Secondary Domain for WhiteDNS

During severe network censorship, DNS and SNI filtering targeting primary domains often prevents users from accessing the web panel and updating their subscription links. WhiteDNS Panel v0.12.0 introduces native support for Secondary Domains (Dual-Domain Failover), enabling seamless operation without interrupting active tunnel sessions.

Key Principle: The secondary domain acts as a hot standby. If your primary domain's subdomains or IP mappings are blocked on certain mobile operators, clients automatically fallback to the secondary domain to retrieve fresh resolver lists and tunnel profiles.

Step 1: Cloudflare DNS Configuration

Before modifying panel settings, log into your Cloudflare dashboard and configure the necessary DNS records for your second domain:

  • A Record: Point panel2.yourdomain.com to your VPS public IPv4 address (Set proxy status to DNS Only / Grey Cloud for tunnel ports, or Proxied / Orange Cloud if strictly using HTTPS port 443 with Origin CA).
  • NS Records: For DNS tunneling protocols (Soar, Cotten, MasterDNS), create NS delegation records (e.g. ns1.yourdomain.com and ns2.yourdomain.com) pointing to your server's IP address.

Step 2: Adding the Secondary Domain in WhiteDNS Panel

  1. Log into your WhiteDNS Web Dashboard with administrator credentials.
  2. Navigate to Settings → Domain & Network Management.
  3. Under Secondary Domain Configuration, enter your new domain name (e.g., panel2.yourdomain.com).
  4. Select SSL Certificate generation method (Automated Let's Encrypt HTTP-01 challenge or custom Cloudflare Origin CA).
  5. Save changes and click Verify & Apply Routing.

Step 3: Verification & Emergency SSH Fallback

If you ever lose access to the web dashboard due to domain propagation issues, you can manage and recover domains directly via the server terminal:

# Check domain routing status
whitedns domain status

# Reset primary domain to default IP
whitedns domain reset --force
Pro-Tip: Always test domain resolution from inside the target network using the nslookup or dig command before distributing new subscription links to users.