yourname.wifipadi.com. If you own a domain, you can put your guest portal and your dashboard on your own address instead — so guests see wifi.yourcompany.com when they connect.
Go to Settings → Custom domains. There are two separate slots:
You can set one without the other.
Before you start
Two requirements catch most people out, and both fail in confusing ways if you guess. You will also need access to wherever your domain’s DNS is managed — Cloudflare, Namecheap, GoDaddy, your web developer, or whoever set up your website.Setting it up
1
Enter the hostname
In Settings → Custom domains, type the subdomain you want into the relevant slot and select Configure. Nothing changes for your guests yet.
2
Add the two DNS records
We now show you a CNAME and a TXT record, each with its name and value. Add both at your DNS provider exactly as shown.The CNAME points your subdomain at us. The TXT record proves you own the name — without it, anyone could claim your domain.
Some DNS providers ask only for the part before your domain. If the name we show is
wifi.yourcompany.com, enter just wifi. If it is _wifipadi-verify.wifi.yourcompany.com, enter _wifipadi-verify.wifi.3
Verify
Select Verify DNS. If it fails, wait a few minutes and try again — DNS changes take time to spread across the internet, sometimes up to an hour. The page tells you exactly what it could not find.
4
Update your routers, if you use MikroTik
If you changed your captive portal domain, MikroTik routers need their installer command run again, because the portal address is written into the router itself.Nano Pi gateways pick up the change on their own within a minute. Nothing to do.
yourname.wifipadi.com address keeps working. Setting a custom domain adds an address, it does not remove one.
Keeping it working
We recheck your DNS every day. If a check fails, here is what happens:
Once you have fixed the DNS, go back to Settings → Custom domains and select Verify DNS. We do not retry a failed domain automatically, so this step is needed to switch your address back on.
If verification keeps failing
CNAME must point to domains.wifipadi.com
CNAME must point to domains.wifipadi.com
Either the CNAME is missing, or it is an A record instead. Check the record type at your DNS provider — it must say CNAME.If your provider refuses to create a CNAME, you are probably trying to use your bare domain rather than a subdomain.
TXT verification token does not match
TXT verification token does not match
The TXT record exists but holds the wrong value. Copy it again from the settings page — it is easy to miss a character, and some providers add quote marks that should not be there.If you changed the hostname after first configuring it, we issued a new token. The old TXT value will no longer work.
Required DNS record was not found
Required DNS record was not found
We could not see the record at all. Most often it simply has not spread yet — wait and try again.If it has been more than an hour, check that you added the record to the same domain you typed into WifiPadi, and that your provider is not still showing it as pending.
Enter a valid fully qualified subdomain
Enter a valid fully qualified subdomain
You entered a bare domain such as
yourcompany.com. Use a subdomain like wifi.yourcompany.com.