This article will give you a complete walk-through for setting up your One.com domain on your Begin app. The entire process should take no longer than 10 minutes.
Although you may use a free registrar-based DNS to host your domain on Begin such as Godaddy, Namecheap, One.com, etc., Route53 is the preferred registrar and DNS management system for Begin users:
- It's integrated with Amazon's other cloud services.
- Your DNS will resolve from 15+ locations worldwide, making your website faster for your end-users.
- Route53 is a DNS management system (Smart DNS) compared to all the others, which are merely domain registrars with a limited feature set for manipulating DNS.
Check out our guide for Setting up an AWS Route53 domain on Begin
This article assumes that you have already:
- signed up for One.com
- purchased the domain of your choice
- created your Begin app to map your domain
The first step in domain mapping is to enter the domains you'll be using.
Begin's first-class support for staging environments means you'll need to add a staging domain (or subdomain), too.
Say your domain is
www.example.com. We'd suggest keeping it simple and setting your staging domain to staging.example.com – but you can also opt to configure it to be
examplestaging.net if you prefer.
This article is for users that want to map a
naked domain. A naked domain (also referred to as a zone apex) is simply a domain set up to respond to requests without a subdomain. For example:
https://begin.comis a web address using a naked domain
https://docs.begin.comhas a subdomain and is thus not a naked domain.
One.com has the ability to add ALIAS records (also sometimes called
A ALIAS), in order to create a mapped naked domain.
In the next step, you'll enter the first two values in your DNS provider's interface, which will prove you own your domains and generate your SSL certificates.
In this step, you'll need to add two
CNAME values to your One.com DNS in order to verify your ownership of the domain and generate your SSL certificates for HTTPS.
Head back to the One.com console and navigate to the
DNS records page for your specific domain. During the SSL verification step, the first part of the name gets entered as your
CNAME subdomain, and the value is inputted as the value. For instance, when you're provided the following
You'll add a CNAME subdomain of
_2f9b34277e4b159e0beaa859e8802a93within your One.com
Then, set its
Is an alias of to
⚠️ Leave the trailing period off!
Due to the eventually consistent nature of DNS-based verification, it may take a few minutes for your changes to get picked up. Check back after a few minutes, and your values should be green, and you should be able to complete the next and final step.
If for some reason after more than a few minutes your domains haven't verified, make sure that you've correctly entered the settings into your DNS.
In the final step, you'll add the final
ALIAS records to your One.com. This points your domain at your Begin app.
When you provide the
- Switch to
Is an alias of:
When you provide the
- Switch to
- Find out the IP address of the given cloudfront URL (
http://pi1f6fddqd0dje.cloudfront.net) using a tool like 24x7.com
- Lastly in the Will point to: section, add the IP address.
Now we're done! You can check to see if your domains are online with this DNS Checker tool.
Keep in mind that it make take a few hours for DNS to fully propagate so be patient.
Something not looking right? No sweat, DNS can be finicky. If you need to hit the reset button, just click Start over (or, if you've finished mapping your domain, Delete domain mapping).
Your app will then be restored to its original
yourappname.begin.app URLs, and you'll be able to re-map your domain again.