As part of a corporate network migration, DNS was top of the list.
MyDNSConfig 3.0.1 was the source and Route 53 being the preferred destination.
Step are very straightforward:
- Login to AWS Account and navigate to Route 53
- Create ‘Hosted Domain’ > enter domain name and a comment (good housekeeping)
- Select ‘Import Zone File’
- SSH to the MyDNSConfig server
- Export a record by the following command:
Which outputs the entire zone file e.g.
$TTL 86400 ; Zone: domain.com. (#213) ; Created by "mydnsexport domain.com." ; Thu Jan 19 16:11:16 2017 $ORIGIN domain.com. @ IN SOA ns1.dnsdomain.net. . ( 2016050607 ; Serial 28800 ; Refresh 7200 ; Retry 604800 ; Expire 86400 ) ; Minimum domain.com. 86400 IN A 10.10.10.10 domain.com. 86400 IN MX 5 ALT1.ASPMX.L.GOOGLE.CO M. domain.com. 86400 IN MX 5 ALT2.ASPMX.L.GOOGLE.CO M. domain.com. 86400 IN MX 1 ASPMX.L.GOOGLE.COM. domain.com. 86400 IN MX 10 ASPMX2.GOOGLEMAIL.COM . domain.com. 86400 IN MX 10 ASPMX3.GOOGLEMAIL.COM . domain.com. 86400 IN NS ns1.dnsdomain.net. domain.com. 86400 IN NS ns2.dnsdomain.net. domain.com. 86400 IN TXT "google-site-verification=dfg645645745675G6t6DtljVj0dsft654634ter5345" www.domain.com. 86400 IN A 10.10.10.10
6. Highlight the exported records (copy everything from the first A record to the last record)
7. Paste the zone file into ‘Zone File’ in Route 53
8. Select Import
9. Login to the domain registrar and update Name Servers to those specified by Route 53 (found in ‘Hosted Domain’)
That’s all there is to it.
Few things to note:
- Route 53 will disregard any NS records
- If there are mutliple TTL values Route 53 will not import. Paste the records into e.g. Notepad++ and do a find/replace to make all values the same e.g. 86400
- Route 53 will pick up any errors, typos in your zone file and report back on screen
- This was a very manual process but helped with mitigation of redundant domains