Your website will be accessible with . To access it with do this three extra steps: http https with the AWS Certificate Manager for your domain Create an certificate for your "root" S3 bucket. Associate the certificate to it Create an AWS CloudFront distribution Point the record of your apex domain to the new CloudFront distribution ALIAS How to Point a Naked Domain - Not Registered with Route 53 - to an AWS S3 Hosted Static Website So people can access your website through example.com instead of www.example.com . In this post, we're going to connect an with an AWS S3 hosted website. The naked domain is bought in a domain name registrar other than AWS Route 53. In this case . apex domain OVH For other registrars the steps are similar. Apex domains, generally, cannot make use of records. Allowed are A or records, pointing to static IPs. This makes it harder to use our naked domain for our website: . This is because of the dynamic nature of AWS S3 instances. They expose a subdomain endpoint, so they can route the internal traffic with freedom. CNAME AAAA example.com Let's start. Copy your current zone file , go to: , and reduce the (Time to Live). The authoritative name servers cache will expire faster now. This is good because we're going to change the (Name Server) records. Log in to your OVH account Domains > DNS zone TTL NS Now click on: , and copy your RRs (Resource Records). DNS zone > Change in text format It should look like: @ dns18.ovh.net. tech.ovh.net. ( ) dns18.ovh.net. ns18.ovh.net. mx3.mail.ovh.net. mx1.mail.ovh.net. mx2.mail.ovh.net. ??? ??? " |www.rubenbelow.com" "v=spf1 include:mx.ovh.com ~all"
_autodiscover._tcp mailconfig.ovh.net.
_imaps._tcp ssl0.ovh.net.
_submission._tcp ssl0.ovh.net.
autoconfig mailconfig.ovh.net.
autodiscover mailconfig.ovh.net.
ftp rubenbelow.com.
imap ssl0.ovh.net.
mail ssl0.ovh.net.
pop3 ssl0.ovh.net.
smtp ssl0.ovh.net.
www ??? $TTL 3600 IN SOA 2019112215 86400 3600 3600000 300 IN NS IN NS IN MX 100 IN MX 1 IN MX 5 IN A IN AAAA IN TXT 1 600 IN TXT IN SRV 0 0 443 IN SRV 0 0 993 IN SRV 0 0 465 IN CNAME IN CNAME IN CNAME IN CNAME IN CNAME IN CNAME IN CNAME IN CNAME * Some values are replaced with: ??? In the next step we're going to import our entries in AWS Route 53. Before, let us delete some entries. Records to delete: dns18.ovh.net. ns18.ovh.net.
... ??? ???
...
www ??? IN NS IN NS IN A IN AAAA IN CNAME Create an AWS Route 53 Hosted Zone , go to Route 53, and click on: . As: , use the name of your apex domain: . Log in to your AWS console Create Hosted Zone Domain Name example.com Modify your DNS file SOA record Before starting with the next step we need to change the (Start of Authority) record to match the new one. SOA Change: @	IN SOA dns18 . tech . ( ) .ovh .net .ovh .net 2019112215 86400 3600 3600000 300 To the SOA record in your new Hosted Zone. The entry should be now like: @	IN SOA ns awsdns com. awsdns-hostmaster.amazon.com. -289. -36. 1 7200 900 1209600 86400 Import your DNS file into Route 53 Now that we have a fresh hosted zone we'll import the RRs we exported from OVH. Do not import the previously deleted NS , A , and AAAA records! Click on your new Hosted Zone: (you'll see a list of RRs) example.com Click on: Import Zone File Paste your previously exported records DNS Import your records DNS If you get: . Delete the mismatching from the zone file. "Error parsing zone file: One resource cannot have multiple distinct TTL values" TTL From: IN TXT 600 "v=spf1 include:mx.ovh.com ~all" To: TXT IN "v=spf1 include:mx.ovh.com ~all" Add an ALIAS record So far, so good. Now we add an record for the naked domain; pointing to our AWS S3 bucket. A ALIAS example.com It should be like this but  with an S3 bucket URL instead of a CloudFront URL Do the same now with an AAAA record. Add a CNAME record Add a record for your subdomain pointing to your apex domain: . CNAME www example.com It should be like this Get your new NS entries Get the values of your entry. We're going to use them at OVH in the next step. NS They should be like: ns- .
ns- .
ns- .
ns- . 289 .awsdns-36 .com 1715 .awsdns-22 .co .uk 1241 .awsdns-27 .org 740 .awsdns-28 .net Add your new AWS NS values to your domains registrar In your OVH account go to: DNS servers Delete the old OVH records NS Add your new AWS records NS Good to go. Troubleshooting The changes will take some time to propagate (sometimes up to 24h). We can check the state of the DNS (Domain Name Server) update on: Zonemaster MXToolBox DNS Checker If the DNS update is done but you cannot access through your computer, it could be that your ISP (Internet Service Provider) still did not update their RR cache. In this case, you should be able to . example.com access your website through a VPN Thanks for learning with this tutorial. Follow me on GitHub . If for some casual the indications did not work for you; don't mind to drop me a line with the infringing points . I'll update the post correspondingly. References Migrating DNS Migrate DNS Domain in Use How to Resolve Error in AWS Route 53 Import Zone File More Posts Welcome

Amazon

Naked

rubenbelow.com

Read My Stories

Too Long; Didn't Read

Developers: Build Less. Deliver More. [Learn how]	

DNS Migration: Forwarding an External Registered Apex Domain to an AWS S3 Bucket

Too Long; Didn't Read

Companies Mentioned

Rubén Below

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

DNS Migration: Forwarding an External Registered Apex Domain to an AWS S3 Bucket

Too Long; Didn't Read

Companies Mentioned

Rubén Below

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

RELATED STORIES