Search…
DNS and nameservers
How to set up external DNS services to work with ReleaseHub.

How ReleaseHub routes traffic to your environments

ReleaseHub creates dynamic routing entries in our proprietary [email protected] routing infrastructure for every environment. When new ephemeral or permanent environments are created by ReleaseHub, we update a routing table stored in DynamoDB, which is then checked on every request made to Cloudfront with a [email protected] program. This way, we can instantly route and reroute traffic without waiting for propagation delays or TTLs to expire.
In order to correctly create a hostname for a dynamic service, ReleaseHub talks to the ALB ingress controller in AWS to create the correct routing entry and point requests to the correct environment. For static sites, ReleaseHub takes the bucket hostname and path, including a list of any assets written to S3 for the version being deployed, and adds those entries to our routing table.
For self-hosted customers, we use the following pattern to create ephemeral hostnames:
service_name-${randomness}-app_name.yourdomainname.com
Here is an example ephemeral hostname for an app called "Example" and a service called "Test":
test-ted3352-example.yourdomainname.com
Permanent environment hostnames are usually static and could be something like the following examples show:
www.yourdomainname.com
www.staging.yourdomainname.com
For hosted customers, all of the cluster communication, routing, and DNS traffic occur inside ReleaseHub's customer account in AWS. For self-hosted, ReleaseHub-managed customers, all of the cluster communication, routing, and DNS traffic occur inside their own AWS account. For customers who might have a third-party DNS requirement or existing deployment, we still require an AWS Route53 zone, but we can integrate as shown in the next sections.

Required setup for all externally hosted DNS providers

Before setting up your external DNS provider, you must create a subdomain on a hosted zone in AWS where you'd like your environments to be accessed.
Navigate to the Route53 service in AWS by searching for it in the Services drop-down.
Click "Hosted Zones"
Click Create Hosted Zone, then fill in "Domain name" and leave the type set to "Public Hosted Zone". Click Create.
Fill in the details of the subdomain you want your ReleaseHub apps to run on. In this example, ephemeral environments will be hosted on the releasehub.gethandsup.com subdomain. In our prior example, setting this would result in an ephemeral environment running here:
test-ted3352-example.releasehub.gethandsup.com

Set up Cloudflare

For users who have DNS routed through Cloudflare, here are the steps you need to take to configure things to work correctly with ReleaseHub.

Create NS records to point to your Route 53 subdomain or hosted zone

You will need to know the nameservers that were created for your hosted zone before finishing this set up. You can find the nameservers for your hosted zone by selecting the zone and viewing the details from your Route53 console.
Navigate to the "DNS" section in the Cloudflare menu and create NS records that point to your Route53 hosted zone or subdomain.
In this example, the subdomain where ReleaseHub environments will be run is releaseapp. Set the "Name" field to the subdomain or hosted zone you created. For every nameserver for that hosted zone, create an NS record. Leave the "TTL" field set to "auto".
ReleaseHub will handle all the certificate creation, Cloudfront (via [email protected]) routing table updates, and DNS entries for you.
Copy link
On this page
How ReleaseHub routes traffic to your environments
Required setup for all externally hosted DNS providers
Set up Cloudflare