Custom domains

A guide to setting up your domain to point to pico services


All of our services support custom domains and they all work the exact same way. The way it works is you provide a CNAME record and a corresponding TXT record. Then when any of our web services receives traffic from that domain, we check the TXT record to figure out what content to serve the user.

HTTPS will be automatically enabled and a certificate will be retrieved from Let's Encrypt. In order for this to work, 2 DNS records need to be created:

CNAME for the domain to the pico service (subdomains or DNS hosting with CNAME flattening) or A record.

# prose.sh

Setting up a custom domain for prose is the same as all the other services, except for pgs -- more on that later.

CNAME subdomain.yourcustomdomain.com -> prose.sh

Resulting in:

subdomain.yourcustomdomain.com.         300     IN      CNAME   prose.sh.

And a TXT record to tell Prose what blog is hosted on that domain at the subdomain entry _prose

TXT _prose.subdomain.yourcustomdomain.com -> yourproseusername

Resulting in:

_prose.subdomain.yourcustomdomain.com.         300     IN      TXT     "hey"

Depending on your DNS, this could take some time to fully switch over. We have an endpoint to check whether or not custom domains are setup:

curl -vvvv https://prose.sh/check?domain=xxx

# pgs.sh

pgs.sh is a little different in that we allow the user to configure custom domains per project so it's a little different.

And a TXT record to tell pgs what project is hosted on that domain at the subdomain entry _pgs.

subdomain.yourcustomdomain.com.         300     IN      CNAME   pgs.sh.
_pgs.subdomain.yourcustomdomain.com.    300     IN      TXT
"{user}-{project}"

# Example: Top-Level Domain

Resulting in:

erock.io.         300     IN      CNAME   pgs.sh.
_pgs.erock.io.    300     IN      TXT     "erock-kittens"

# Example: Subdomain

Resulting in:

meow.erock.io.         300     IN      CNAME   pgs.sh.
_pgs.meow.erock.io.    300     IN      TXT     "erock-kittens"

# My DNS does not support CNAME flattening

In that case, you need to get the IP address of the service you want to point to and then use that as an A record.

WARNING: We make no guarantees that our IP addresses will stay the same. Use at your own risk!

<< PREV
Join
NEXT >>
pgs.sh
Home
Sitemap
Getting started
How it works
File uploads
Custom domains
pgs.sh
tuns.sh
imgs.sh
prose.sh
pastes.sh
feeds.sh
Images
IRC
API Tokens
FAQ
Lab
Plain text lists
About us
Abuse
Operations
Privacy policy