Connecting your AWS Route 53 domain

Subscription note

If you're not on a paying plan you will not receive SSL or Root Domain Redirection. Due to this, you'll only see one DNS record.

This document has a prerequisite

You'll need to already have completed the steps in our custom domain configuration document.

With the 1-3 records you have within your Unstack settings page, you'll follow these steps. You'll want to note down the records you'd received from Unstack as we'll be copying and pasting them into AWS Route 53.

Here's a run-down of how we'll reference these records in a human-friendly way throughout this document:

Record Name Record Type Record Description
WWW Record CNAME This record has a HOST of "www" and is named the www record since it hosts/establishes the hosting of your domain.
Root Domain Record A Record This record has a HOST of either nothing (blank) or "@" depending on your host. Within GoDaddy, you'll use "@."
SSL Record CNAME This record has a HOST which begins with an underscore (_) you'll need to verify the HOST and VALUE are both correct.
  1. Login and go to the AWS Route 53 Dashboard for hosted zones.
  2. Select the hosted zone (domain) you'd like to connect to Unstack.
  3. You'll navigate to the Records (1) tab within the hosted zone:
    Route_53_Console_Hosted_Zones_2021-02-01_at_8.15.29_PM.jpg
  4. Now, for the WWW record, we'll follow this process:
    1. Click the Create record button (2).Route_53_Console_Hosted_Zones_2021-02-01_at_8.18.35_PM.jpg
    2. Under Routing policy select Simple routing.
    3. In the Record name field (3), enter "www".
    4. In the Record type field (4) of a blank row, select CNAME from the drop-down.
    5. In the Value field, enter the Value for your WWW Record found on your Unstack settings page:
      Image_2021-02-01_at_2.05.00_PM.jpg
    6. Click Create records to save the record to your settings.
  5. Next, we'll add the SSL Record following this process:
    1. Click the Create record button (2).Route_53_Console_Hosted_Zones_2021-02-01_at_8.18.35_PM.jpg
    2. Under Routing policy select Simple routing.
    3. In the Record name field (3), enter the Name for your SSL record which begins with an underscore (_) found on your Unstack setting page:
      Image_2021-02-01_at_2.02.16_PM.jpg
    4. In the Record type field (4) of a blank row, select CNAME from the drop-down.
    5. In the Value field, enter the Value for your SSL Record found on your Unstack settings page:
      Image_2021-02-01_at_2.05.00_PM.jpg
    6. Click Create records to save the record to your settings.
  6. Last, we'll add the Root Domain Record following this process:
    1. Click the Create record button (2).Route_53_Console_Hosted_Zones_2021-02-01_at_8.18.35_PM.jpg
    2. Under Routing policy select Simple routing.
    3. In the Record name field (3), enter "@" or leave it blank.
    4. In the Record type field (4) of a blank row, select A from the drop-down.
    5. In the Value field (5), enter the Value for your A Record which will follow this format ##.###.##.### found on your Unstack settings page:
      Image_2021-02-01_at_2.05.00_PM.jpg
    6. Click Create records to save the record to your settings.
  7. Once you've completed this configuration it may take 24-48 hours for your domain connection to finalize and be recognized as "Properly configured" within Unstack.

And, done! If you need help, please reference this document from Amazon Web Services and contact the AWS support team.

Troubleshooting

It's showing as "Pending" within Unstack

If: All records are added, 24-hours has passed, and proxying is disabled, send a screenshot of your DNS to Unstack support for personalized support!

An ___ record with that host already exists.

This error means that this host is already present as a DNS record within your Amazon Web Services account. Unstack cannot advise on the deletion of records.

We advise you either (1) contact your technical manager for help in deleting the issue-causing record(s) or (2) contact Amazon Web Services support for further help.

Unsecure domain

Please ensure you've activated SSL for your custom domain and have inputted the respective SSL Record. If you have, it can take up to 48-hours to activate.

Articles in this section

Was this article helpful?
0 out of 0 found this helpful
Share