Table of Contents
Customer facing vanity domains
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.
Vanity domains as subdomains
The apps almost always use a subdomain because it improves Google search results and SEO, so require a CNAME change. We only support a single vanity domain for each app.
You'll need to point this domain to our Fastly CDN (pugpig.map.fastly.net) using your DNS provider. An example entry would be:
Single feed:
reader.acme.com 300 IN CNAME pugpig.map.fastly.net
Multiple feeds:
en.reader.acme.com 300 IN CNAME pugpig.map.fastly.net
fr.reader.acme.com 300 IN CNAME pugpig.map.fastly.net
Wildcard:
*.mydomain.com 300 IN CNAME pugpig.map.fastly.net
Whilst we support vanity domains it can't be a deep url / vanity url. It has to be the root of a subdomain.
Note: If you had done this in the past before we supported HTTPS, you would have CNAME'd to global.prod.fastly.net - please update your CNAME if you need HTTPS.
Vanity domains as APEX domains
The sites often use an APEX domain (without the www). In some cases if your brand doesn't have a website, you may need one for an app. For an APEX domain (e.g acme.com), you need to add the following A Records:
- 151.101.1.72
- 151.101.65.72
- 151.101.129.72
- 151.101.193.72
and ideally the following 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.acme.com) you also need the relevant CNAME for the subdomains. If you provide www.acme.com and acme.com, we will always redirect to the www version.
For example:
www.acme.com 300 IN CNAME pugpig.map.fastly.net
HTTPS Certificates
We will handle all of the HTTPS certificates, and once it is done you can check to ensure you have a lovely green A+ rating by using https://www.ssllabs.com/ssltest/index.html
CAA Records
If you are using DNS CAA records to restrict the issuing of certificates, 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. Without this we will be unable to set up the SSL on the vanity domain. For example add this in addition to existing CAA records
acme.com 300 IN CAA 0 issue "globalsign.com"
Delegating Fastly Domains
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 need to have the following subdomains delegated to Pugpig (Customer: 3RIzR9GCn3aTXou8ZfjUFo):
<subdomain1.yourdomain.com>
<subdomain2.yourdomain.com>
We've cc'ed in the Pugpig team in case you have any questions
Thanks,
<Your Name>