More than a year since I have written in here… But past is the past, and going forward, there are many things I want to share, so now I have set a goal to share as much as I can through this, so lets keep on grinding. And I’ll start with a Jocko Willing quote:
Extreme ownership is an attitude of not making excuses for anything.
And with that, let’s get down to business.
AWS – Route 53
It comes from port 53 (which is the DNS port in UDP/TCP) not from the Route 53 in USA, in order to configure you can either buy the domain directly from AWS (which is very convenient) but you can get really good deals in Namecheap or GoDaddy sometimes. Anyways, the way I use it is for public hosted (you can also use it for private hosted VPC) once you set the domain you will need to relay the operations by changing the name servers.
Once you got that you are all set, you can test the name resolution
$ nslookup -type=SOA elavena.mx
primary name server = ns-1609.awsdns-09.co.uk
responsible mail addr = awsdns-hostmaster.amazon.com
serial = 1
refresh = 7200 (2 hours)
retry = 900 (15 mins)
expire = 1209600 (14 days)
default TTL = 86400 (1 day)
And it is ready. You now have full control of it via AWS on Route53; adding records just a few clicks away.
Azure – DNS Zones
Azure has a little more to it, as it can be fully managed, you can link it to your AppService, VM or Service; You can also generate certificates for your apps for your domains too and link them directly to your Service (for HTTPS). It start also by creating a DNS Zone, once you create it Azure will give you the list of Name Servers, and you will need to update the same info in your your DNS management from your provider (like above picture).
Once that is set, you will have also total control of DNS records for that domain.
Hope this helps when looking for a solution to extend and control your DNS from a single point.