This guide hopes to show you how to setup a Digital Ocean Droplet (server) as a Sub Domain on an existing AWS domain. I am setting up a Digital Ocean Domain as a sub domain (both existing) and using the sub domain (Digital Ocean server) as a self-service status page. I have setup both domains with SSL certificates and strong Content Security Policies and Public Key Pinning.
DO: Obtain the IP addresses for your Digital Ocean Droplet (that will be the sub domain). If you don’t already have a Digital Ocean Droplet click here (and get 2 months free).
This AWS guide was a handy start Creating a Subdomain That Uses Amazon Route 53 as the DNS Service without Migrating the Parent Domain.
From the AWS Route 53 screen, I clicked Get started now.
From here you can Create a Hosted Zone.
Create a Hosted Zone.
A sub domain can be created on AWS Route 53.
I created a route 53 A Name record and pointed it to a known Digital Ocean droplet IP address.
I created an A Name record on Digital Ocean for the droplet (e.g status.______.com).
I created an IPV6 (AAAA) record on Digital Ocean for the droplet?
I could not ping the server so I added the digital ocean name servers to the route 53 record set out of desperation.
Final Route information on AWS.
Hmm, nothing works as of yet.
https://www.whatsmydns.net is not showing movement yet.
Time to contact AWS for advice.
I tried to post an help post on the AWS forums but apparently, a user who has been paying AWS for 6 months does not have the right to post a new forum thread.
I posted a few help questions on twitter and I’ll try these out tonight.
I created a record set for the parent domain on AWS and A record for the Digital Ocean subdomain with no luck.
This post will be updated soon.
v1.9 added info on let’s encrypt (10:38pm 29th July 2017 AEST)
Donate and make this blog better
Ask a question or recommend an article