The following guide covers steps to setup your custom domain with "domain masking", where visitors to your PublicInput.com page see your custom domain in their URL bar throughout their usage of the site. It is a more involved process than a "redirect", which simply re-routes traffic to your PublicInput.com site.

***Please note custom domains may take up to three business days to process and setup due to registrar behavior and DNS caching.***

To get started, fill out the custom domain request form here

Provide the custom domain name and the project page, topic, or engagement hub you would like to point the URL to within PublicInput.com.

Option A: Re-routing this domain's DNS name servers

This option works best for new domains, or when you'd like PublicInput to procure a domain on your behalf.

1. Log in to your domain registrar account (i.e. GoDaddy, Google Domains, or other) and remove the existing nameservers for your custom domain.

Here's a quick example of what you might have for current name servers.

ns55.domaincontrol.com
ns56.domaincontrol.com

2. Replace with the following nameservers:

Nameserver 1

amir.ns.cloudflare.com

Nameserver 2

gene.ns.cloudflare.com

Not sure how to do this? Here are links to articles covering how to change your domain nameservers in GoDaddy, Network Solutions, Google Domains, NameCheap, Bluehost, and Hostgator.

3. Save your changes.

4. Notify PublicInput.com support you have made these changes.

We'll look for your domain routing to begin pointing to our DNS endpoint, and setup custom routing for your site. As noted above, some registrars may take 24-48 hours to update, and we have to verify domain ownership with our cloud infrastructure provider after that happens, so please plan for 2-3 business days for these changes.

Option B: Adding DNS records and an SSL certificate

This option works best if you would like to create a subdomain like engage.dc.gov or use a domain that has other active subdomains. To complete this option, you'll need to have your IT team add specific DNS records and setup an SSL certificate.

Here are the records you'll need to create:

A Record

In order to properly route traffic to this domain, you'll need to point the A record for your domain or subdomain to 168.61.170.253.

(e.g. engage.mayberrync.gov : 168.61.170.253)

TXT Record

In order to verify domain ownership, you'll place a new TXT entry in your DNS hosting provider matching the following:

TXT -> asuid.www or asuid.{subdomain} -> 94A0E4870F1C6E6A1FF0DF4380DD9C8EAC8

These entries are summarized for quick reference here:

DNS Entry Type

Entry

Points to

A

@ or {subdomain}.{domain}.{tld}

168.61.170.253

TXT

asuid.www or asuid.{subdomain}

94A0E4870F1C6E6A1FF0DF4380DD9C8EAC8

SSL

To complete SSL setup, we'll need to either use an SSL certificate that you own for this domain, or procure an SSL certificate for you. To kick off this process, first submit the Custom Domain Request Form, then email [email protected] to let them know you'll need to coordinate SSL provisioning. We'll be in touch from there to provide information needed to setup your SSL certificate.

Related:

Set up a custom domain for sending emails

Did this answer your question?