Cloudflare DNS for a Mumble subdomain (mumble.yourdomain.com)

Updated: February 2026

Using your own domain for Mumble makes onboarding easier (“connect to mumble.yourdomain.com”). With Cloudflare, the key rule is: voice traffic is not HTTP, so the record must be DNS-only (grey cloud), not proxied.

Rule: Cloudflare must not proxy the Mumble hostname. Set the record to DNS only.

New to VPS security? Start with our Ubuntu VPS hardening checklist.

What you need

Your domain is managed in Cloudflare
The server’s public IPv4 (and optionally IPv6)
Mumble running and reachable on UDP 64738

1) Create the DNS record

In Cloudflare: DNS → Records → Add record.

IPv4 (recommended baseline)

Type: A
Name: mumble (or voice, your choice)
IPv4 address: your server’s public IPv4
Proxy status: DNS only (grey cloud)

IPv6 (optional)

If your VPS has IPv6 and you want clients to use it:

Type: AAAA
Name: same hostname (mumble)
IPv6 address: your server’s public IPv6
Proxy status: DNS only

2) Verify DNS resolution

From your local machine:

nslookup mumble.yourdomain.com

# Or:
dig +short mumble.yourdomain.com A

If it doesn’t resolve correctly, fix DNS before debugging Mumble.

3) Common mistakes (Cloudflare)

Orange cloud (proxied): Mumble is not an HTTP service; proxying breaks it.
Using a CNAME when you actually need an A/AAAA to your server IP.
Pointing at a private/VPC IP instead of the public IP.

4) If DNS is correct but the server is still unreachable

At that point the issue is usually firewall/routing. Use: Mumble server not reachable (UDP blocked) — fix checklist.

Want a private voice server with your domain?

SecureVoice can set up DNS + a dedicated server (hosted) or do a fixed-scope BYO‑VPS setup.

See Services →