Pugpig CMS Domains

Pugpig is a SaaS platform, so all internal tools used by editorial/marketing/etc will be on a pugpig.com domain. These cannot be changed to be your own domain.

PUGPIG EXPRESS: CMS DOMAINS

Pugpig Express domains are of the form:

<account>-<publication>.express.pugpig.com

For example, acme-weekly.express.pugpig.com

PUGPIG PRO: CMS DOMAINS

If you are using Pugpig Professional, the domains you'll get for access to your CMS are:

<publication>.prod.<account>.pro.pugpig.com
<publication>.stage.<account>.pro.pugpig.com

For example:

weekly.prod.acme.pro.pugpig.com
weekly.stage.acme.pro.pugpig.com

TESTING/STAGING CONTENT DOMAIN:

The original public facing domain for your content and web reader will be:

<account>-<publication>-<endpoint>.content.pugpig.com

For example, in multi-lingual app:

acme-weekly-en.content.pugpig.com
acme-weekly-fr.content.pugpig.com

The public facing content domain should always be HTTPS and used for:

• everything in the admin
• everything in the apps
• for web reader auth endpoint

We strongly recommend this is replaced by your own vanity domain for live content.

DISTRIBUTION SERVICE DOMAIN

When these are available you will log into the distribution service using:
<account>.admin.pugpig.com

Customer Facing Vanity Domains

We strongly recommend you use a domain you control for all customer facing content. In order to do this, you will need to change DNS records to point domains to the correct place.

Important: We provide the HTTPS certificates. If you are using DNS CAA records to restrict the issuing of certificates, please add "globalsign.com" to the allowed list (ideally just for our subdomain if applicable) or we will be unable to set up the SSL on the vanity domain

VANITY DOMAINS FOR APPS

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 FOR SITES

The sites often use an APEX domain (without the www). 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

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

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>