Custom vanity domains
Table of Contents
Vanity domains are mandatory
We strongly recommend you use a domain you control for all customer facing content. It gives you more flexibility and control, and you look more professional. You don't want your customers seeing Pugpig in a domain name in their browser, a newsletter or social media post.
In order to do this, you will need to change DNS records to point domains to the correct place.
Implementing Your Vanity Domain
To set up your custom domain with Pugpig, you'll need to adjust your DNS records to point to our Content Delivery Network (CDN). This process varies slightly depending on whether you're using a subdomain or an apex (root) domain.
Subdomains
For apps, it's common to use a subdomain (e.g., reader.yourdomain.com
) as it can improve SEO performance. To configure this:
DNS Configuration: Create a CNAME record pointing your chosen subdomain to pugpig.map.fastly.net
.
Example DNS Entry for a single feed:
reader.yourdomain.com 300 IN CNAME pugpig.map.fastly.net
Example DNS Entry for multiple feeds:
en.reader.acme.com 300 IN CNAME pugpig.map.fastly.net
fr.reader.acme.com 300 IN CNAME pugpig.map.fastly.net
Example wildcard DNS Entry:
*.mydomain.com 300 IN CNAME pugpig.map.fastly.net
Note: We support a single vanity domain per app.
Apex Domains
If you prefer to use an apex domain (e.g., yourdomain.com
):
DNS Configuration: Add the following A records to your DNS settings:
151.101.1.72
151.101.65.72
151.101.129.72
151.101.193.72
For IPv6 support, include these AAAA records:
2a04:4e42::328
2a04:4e42:200::328
2a04:4e42:400::328
2a04:4e42:600::328
If you also wish to have a subdomain (e.g., www.yourdomain.com
), create a CNAME record:
www.yourdomain.com 300 IN CNAME pugpig.map.fastly.net
Note: If both yourdomain.com
and www.yourdomain.com
are provided, we will redirect to the www
version.
HTTPS Certificates
Pugpig will handle the provisioning of HTTPS certificates for your domain, ensuring secure connections for your users. You can verify the security status of your domain using tools like SSL Labs' SSL Test.
CAA Records
If your DNS setup includes CAA records to restrict certificate issuance, please add globalsign.com
to the allowed list. If you are using a CNAME for the subdomain, the CAA record needs to be added to the parent domain. CAA records are not allowed at the subdomain level if shared with a CNAME record. This ensures we can obtain the necessary SSL certificates for your domain. For example:
yourdomain.com 300 IN CAA 0 issue "globalsign.com"
Note: If you are already using Fastly as your CDN (they're great - you should!) and you have the top level domain on one of your Fastly services, you'll need to get in touch with Fastly Support (support@fastly.com) and ask them to delegate the subdomains to us. Without this, we can't add your domains to our system.
You should send something like this and cc in us. The Pugpig Customer ID 3RIzR9GCn3aTXou8ZfjUFo
is important. They may ask you to add some DNS records to your top level domain to prove ownership if the email request doesn't come from our Fastly account owner.
Dear Fastly Support,
We request the delegation of the following subdomains to Pugpig (Customer ID: 3RIzR9GCn3aTXou8ZfjUFo):
- subdomain1.yourdomain.com
- subdomain2.yourdomain.com
The Pugpig team is cc'd for reference.
Thanks,
[Your Name]