If you already own a domain, you can use it with your pod in an instant. So it will be reachable as e.g.
To use your own domain, you need to add a
ALIAS record and set your pod’s
pikapod.net domain as target.
We will also apply for a free SSL certificate for each mapped domain. This ensures all data going to your pod is encrypted. It can take a few minutes before the pod is reachable from the new domain. You may see an error before this.
Steps to use a custom domain:
- Open Pod Settings and then the Domain tab.
- Enable Custom Domain. Take note of your pod’s
- Ensure no CAA records are set that may prevent us from applying for a SSL certificate. If you already use CAA, please also add
sectigo.com, as mentioned here and
letsencrypt.orgas mentioned here.
Then, depending on if you want to map a subdomain (e.g.
status.my-domain.com) or root (apex) domain (e.g.
CNAMErecord for subdomains:
status.my-domain.com. 3600 IN CNAME xxx-yyy.pikapod.net
ALIASrecord for root domains:
@ 3600 IN ALIAS xxx-yyy.pikapod.net
- Use a tool like DNS Checker to ensure the record on your domains shows your
pikapod.netdomain or the same IP.
- Finally, add the new domain on PikaPod’s control panel. If the setup is correct, it will be verified and saved.
After adding a domain, we will periodically check if DNS is still set up correctly. If there is any issue you will receive a notification.
Only one custom domain can be mapped per pod. If you need additional alias domains, you will need to set up redirects with your DNS provider or a service like Freedirector (free, no signup needed) or redirect.pizza (free tier).
It’s possible to run a pod behind Cloudflare’s proxy after it’s set up. This will send all user requests to Cloudflare first and then to PikaPods. The setup can be useful for pods that get many outside visitors, but will make your experience slower for private pods that are only used after the user logged in.
Enabling proxy feature: When first adding a custom domain via Cloudflare, ensure the Proxy feature is disabled. Else we can’t verify the DNS settings of your domain. You can enable proxying again after adding the custom domain.
Origin SSL Setting: Also ensure that you activate Full SSL encryption (by default, it is set to Flexible SSL, which will cause an infinite loop) or disable the proxy and switch to DNS-only mode.
Web application firewall (WAF): If you use Cloudflare’s proxy feature, it’s possible that our monitoring will get blocked and we can no longer determine if your pod is available on its custom domain. So if you get alert emails, while your pod is available, you can whitelist our control panel to make sure it can do its status checks. See here on how to change access rules. IPs to add will be the ones used by our control panel and may change. Check the current
A (IPv4) and
AAAA (IPv6) records for
api.pikapods.com for numeric IPs.