Musings and Mutterings through the Machines

On DNS

I goofed. In a hurry to transfer my [domain](http://blog.monzell.com) from Google Domains to [AWS](https://aws.monzell.com), I immediately decided to configure my name servers. Now, for reasons that I don't recall why, I decided to use the name servers from another zone file instead of what is created and plugged in the following in AWS's registered domains screen:

ns-553.awsdns-05.net.
ns-241.awsdns-30.com.
ns-1385.awsdns-45.org.
ns-1942.awsdns-50.co.uk.

As it turns out, the name servers *differs* per AWS Zone ID, which meant that at around 5 PM CST, my domain fell off the internet and I stopped getting email. Oops. After realizing my mistake, I copied the correct name servers from my domain zone over and within an hour, my domain is back online and I started to get ~~recruiter spam~~ emails. In my defense, though, with [Google Domains](https://domains.google), I am able to use the same sets of domain servers:

rocinante:blog.monzell.com rilindo$ dig giggle.org -t ns +short
ns-cloud-d4.googledomains.com.
ns-cloud-d1.googledomains.com.
ns-cloud-d2.googledomains.com.
ns-cloud-d3.googledomains.com.

From my standpoint, I should be I should be able to use a consistent, predicable set of name servers for [AWS](https://aws.amazone.com) as well. From what I see, this not possible, as the following demonstrate:

rocinante:blog.monzell.com rilindo$ dig monzell.com -t ns +short
ns-1947.awsdns-51.co.uk.
ns-208.awsdns-26.com.
ns-986.awsdns-59.net.
ns-1338.awsdns-39.org.

rocinante:blog.monzell.com rilindo$ dig rilindo.com -t ns +short
ns-553.awsdns-05.net.
ns-1385.awsdns-45.org.
ns-1942.awsdns-50.co.uk.
ns-241.awsdns-30.com.

I supposed that is what I get for not reading the docs more closely. That said, I am going to find out why AWS name servers aren't a bit more agnostic like Google Domains's were.

Musings and Mutterings through the Machines

Other articles

A Slightly Longer Guide to Setting up a Caching / Forwarding Name Server