Skip to main content
The sub-client portal is fully white-labelled. Your customers see your brand — not PanelDNS — at every touchpoint.

​
Branding settings

Configure branding in your reseller dashboard at Settings → White Label: Changes take effect immediately — no cache to flush.

​
Custom portal domain

Serve the portal from your own domain instead of your-paneldns-domain.com/portal/{slug}.

​
Setup

  1. Go to Settings → White Label → Custom Domain
  2. Enter your desired domain, e.g. dns.acme-hosting.com
  3. Add the DNS record shown to your domain’s DNS:
  4. Click Verify — PanelDNS checks the CNAME and provisions an SSL certificate via Let’s Encrypt automatically
  5. Once verified, the portal is live at https://dns.acme-hosting.com
SSL certificate provisioning typically takes under 60 seconds after the CNAME resolves. If verification fails, check that your DNS TTL has expired and try again.

​
What changes with a custom domain

  • Portal URL: https://dns.acme-hosting.com (no path prefix)
  • SSO login_url in API responses uses your custom domain automatically
  • Password-reset and notification emails link to your custom domain
  • The browser never shows paneldns.com in the address bar

​
Email notifications

Transactional emails sent to sub-clients (welcome, password reset, zone alerts) use:
  • From name — your org name
  • From address — the address configured in Settings → Email
  • Logo — your white-label logo in the email header
If no custom email is configured, emails are sent from PanelDNS’s default address with your org name as the sender name.

​
What is never customisable

  • The underlying API endpoints (/api/v1/, /platform/v1/) — these are infrastructure, not customer-facing
  • Admin panel (/admin) — always uses the platform operator’s branding
  • OpenAPI docs (/api/docs) — developer-facing, not customer-facing, and behind a login