{"id":4255,"date":"2020-11-14T16:52:47","date_gmt":"2020-11-14T22:52:47","guid":{"rendered":"https:\/\/dev.iachieved.it\/iachievedit\/?p=4255"},"modified":"2020-11-14T16:52:47","modified_gmt":"2020-11-14T22:52:47","slug":"migrating-your-nameservers-from-godaddy-to-aws-route-53","status":"publish","type":"post","link":"https:\/\/dev.iachieved.it\/iachievedit\/migrating-your-nameservers-from-godaddy-to-aws-route-53\/","title":{"rendered":"Migrating Your Nameservers from GoDaddy to AWS Route 53"},"content":{"rendered":"<p>I can already hear the rabble shouting, &#8220;Why would you use <a href=\"https:\/\/www.godaddy.com\">GoDaddy<\/a> as your <a href=\"https:\/\/en.wikipedia.org\/wiki\/Domain_name_registrar\">domain registrar<\/a>?!&#8221;  A fair question, but sometimes we don&#8217;t always get to choose our domain registrar (e.g., we inherited it) and aren&#8217;t in a position to change it.  But that doesn&#8217;t mean GoDaddy has to provide DNS management for your domain.<\/p>\n<p>In this post I&#8217;ll show you how to change your domain&#8217;s nameservers from <b>GoDaddy<\/b> to AWS&#8217; <b><a href=\"\">Route 53<\/a><\/b>.  <b>Reader Beware<\/b>:  In this post we are going to change a domain&#8217;s nameservers from one provider (GoDaddy) to another (AWS).  Note that this is <em>not<\/em> (I repeat, <b>not<\/b>) the same as transferring your DNS entries.  I joke about GoDaddy&#8217;s repeated warnings that changing &#8220;nameservers&#8221; is risky, but unless your zone files have been populated in the new environment, you will definitely be in for calamity when your hostnames no longer resolve.<\/p>\n<h2>Getting AWS Route 53 Ready<\/h2>\n<p>Our first step is to create a <b>hosted zone<\/b> in AWS Route 53.  Login in to your AWS account and go to the <a href=\"https:\/\/console.aws.amazon.com\/route53\/v2\/home#Dashboard\">Route 53 dashboard<\/a> and click <b>Create hosted zone<\/b>.<\/p>\n<p><a href=\"https:\/\/dev.iachieved.it\/iachievedit\/wp-content\/uploads\/2020\/11\/createHostedZone.png\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/dev.iachieved.it\/iachievedit\/wp-content\/uploads\/2020\/11\/createHostedZone.png\" alt=\"\" width=\"707\" height=\"456\" class=\"aligncenter size-full wp-image-4257\" \/><\/a><\/p>\n<p>Our zone will be for the domain <b>sonorasecurity.com<\/b> and it will be a <i>public hosted zone<\/i>, in that we want public Internet DNS queries for our domain to be resolved.  Once you&#8217;ve filled in this information, click <b>Create hosted zone<\/b>.<\/p>\n<p><a href=\"https:\/\/dev.iachieved.it\/iachievedit\/wp-content\/uploads\/2020\/11\/publicHostedZone.png\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/dev.iachieved.it\/iachievedit\/wp-content\/uploads\/2020\/11\/publicHostedZone.png\" alt=\"\" width=\"738\" height=\"755\" class=\"aligncenter size-full wp-image-4259\" \/><\/a>  Once the zone is created you&#8217;ll see two DNS entries automatically created, an <code>NS<\/code> entry and an <code>SOA<\/code> entry.<\/p>\n<p><a href=\"https:\/\/dev.iachieved.it\/iachievedit\/wp-content\/uploads\/2020\/11\/nsRecords.png\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/dev.iachieved.it\/iachievedit\/wp-content\/uploads\/2020\/11\/nsRecords.png\" alt=\"\" width=\"926\" height=\"541\" class=\"aligncenter size-full wp-image-4272\" \/><\/a><\/p>\n<p>We&#8217;re interested in the <code>NS<\/code> entry and the fully-qualified domain names listed.  In this example there are <i>four<\/i> nameservers listed:<\/p>\n<ul>\n<li><code>ns-1528.awsdns-63.org<\/code><\/li>\n<li><code>ns-95.awsdns-11.com<\/code><\/li>\n<li><code>ns-658.awsdns-18.net<\/code><\/li>\n<li><code>ns-1724.awsdns-23.co.uk<\/code><\/li>\n<\/ul>\n<p>We&#8217;re going to now use these values in our GoDaddy account to change the nameservers for our domain <code>sonorasecurity.com<\/code>.<\/p>\n<h2>Updating Our Nameservers<\/h2>\n<p>Before we update our domain&#8217;s nameservers, let&#8217;s verify that they are currently hosted by GoDaddy.  In a shell type <code>dig +short NS &lt;your_domain_name&gt;<\/code>.  For example:<\/p>\n<p>[code lang=text]<br \/>\ndig +short NS sonorasecurity.com<br \/>\nns07.domaincontrol.com.<br \/>\nns08.domaincontrol.com.<br \/>\n[\/code]<\/p>\n<p>So far so good.  Now login to your GoDaddy account that manages the domain, and go over to the <a href=\"https:\/\/dcc.godaddy.com\/manage\/dns\">DNS Management<\/a> page. Type in your domain name and select it in the dropdown box.<\/p>\n<p><a href=\"https:\/\/dev.iachieved.it\/iachievedit\/wp-content\/uploads\/2020\/11\/sonoraSecurity.png\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/dev.iachieved.it\/iachievedit\/wp-content\/uploads\/2020\/11\/sonoraSecurity.png\" alt=\"\" width=\"635\" height=\"350\" class=\"aligncenter size-full wp-image-4260\" \/><\/a><\/p>\n<p>Scroll down and find the <strong>Nameservers<\/strong> section and next to <strong>Using default nameservers<\/strong> click the <strong>Change<\/strong> button.<\/p>\n<p><a href=\"https:\/\/dev.iachieved.it\/iachievedit\/wp-content\/uploads\/2020\/11\/changeNameServers.png\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/dev.iachieved.it\/iachievedit\/wp-content\/uploads\/2020\/11\/changeNameServers.png\" alt=\"\" width=\"375\" height=\"234\" class=\"aligncenter size-full wp-image-4274\" \/><\/a><\/p>\n<p>Here is where it becomes comical how many times GoDaddy implores us not to try to change nameservers.  The first page warns you that <i>Changing nameservers is risky<\/i>.  While that is true if you don&#8217;t know what you&#8217;re doing, you&#8217;re a professional, so click on <strong>Enter my own nameservers (advanced)<\/strong>.<\/p>\n<p><a href=\"https:\/\/dev.iachieved.it\/iachievedit\/wp-content\/uploads\/2020\/11\/enterMyOwnNS.png\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/dev.iachieved.it\/iachievedit\/wp-content\/uploads\/2020\/11\/enterMyOwnNS.png\" alt=\"\" width=\"943\" height=\"625\" class=\"aligncenter size-full wp-image-4262\" \/><\/a><\/p>\n<p>You&#8217;ll be presented with a form for entering our AWS nameserver FQDNs.  Here it is important to take note to <em>not<\/em> add the period after the FQDN (GoDaddy will give you an Unexpected Error Occurred message if you try).<\/p>\n<p>Enter all of the nameservers listed in the AWS NS record and click <strong>Save<\/strong>.<\/p>\n<p><a href=\"https:\/\/dev.iachieved.it\/iachievedit\/wp-content\/uploads\/2020\/11\/myOwnNS.png\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/dev.iachieved.it\/iachievedit\/wp-content\/uploads\/2020\/11\/myOwnNS.png\" alt=\"\" width=\"931\" height=\"637\" class=\"aligncenter size-full wp-image-4263\" \/><\/a><\/p>\n<p>Once again we get a warning about our risky behavior!  Yes, yes.  Check, <strong>Yes, I consent<\/strong> and click <strong>Continue<\/strong>.<\/p>\n<p><a href=\"https:\/\/dev.iachieved.it\/iachievedit\/wp-content\/uploads\/2020\/11\/consentToUpdate.png\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/dev.iachieved.it\/iachievedit\/wp-content\/uploads\/2020\/11\/consentToUpdate.png\" alt=\"\" width=\"625\" height=\"413\" class=\"aligncenter size-full wp-image-4264\" \/><\/a><\/p>\n<p>After clicking <strong>Continue<\/strong> you will likely see a banner at the top of the DNS management page indicating a change is in progress.  Once completed you&#8217;ll see your nameservers listed, and GoDaddy indicating that &#8220;We can&#8217;t display your DNS information because your nameservers aren&#8217;t managed by us.&#8221;<\/p>\n<p>Now, in a terminal you can type <code>dig +short NS &lt;your_domain_name&gt;<\/code> and you should see your nameservers updated, like this:<\/p>\n<p>[code lang=text]<br \/>\ndig +short NS sonorasecurity.com<br \/>\nns-1528.awsdns-63.org.<br \/>\nns-1724.awsdns-23.co.uk.<br \/>\nns-658.awsdns-18.net.<br \/>\nns-93.awsdns-11.com.<br \/>\n[\/code]<\/p>\n<p>And there you have it, your domain&#8217;s DNS entries can now be managed with AWS Route 53!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I can already hear the rabble shouting, &#8220;Why would you use GoDaddy as your domain registrar?!&#8221; A fair question, but sometimes we don&#8217;t always get to choose our domain registrar (e.g., we inherited it) and aren&#8217;t in a position to change it. But that doesn&#8217;t mean GoDaddy has to provide DNS management for your domain. [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[21,108],"tags":[110],"class_list":["post-4255","post","type-post","status-publish","format-standard","hentry","category-devops","category-route-53","tag-godaddy-aws-route-53"],"_links":{"self":[{"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/posts\/4255"}],"collection":[{"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/comments?post=4255"}],"version-history":[{"count":20,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/posts\/4255\/revisions"}],"predecessor-version":[{"id":4283,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/posts\/4255\/revisions\/4283"}],"wp:attachment":[{"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/media?parent=4255"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/categories?post=4255"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/tags?post=4255"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}