Creating Resource Record Sets By Importing a Zone File
If you're migrating from another DNS service provider, and if your current DNS service provider lets you export your current DNS settings to a zone file, you can quickly create all of the resource record sets for an Amazon Route 53 hosted zone by importing a zone file.
A zone file uses a standard format known as BIND to represent resource record sets in a text format. For information about the format of a zone file, see the Wikipedia entry Zone file. Additional information is available in RFC 1034, Domain Names—Concepts and Facilities section 3.6.1, and RFC 1035, Domain Names—Implementation and Specification section 5.
If you want to create resource record sets by importing a zone file, note the following:
The zone file must be in RFC-compliant format.
The hosted zone must be empty except for the default NS and SOA records.
The domain name of the resource record sets in the zone file must match the name of the hosted zone.
Amazon Route 53 supports the
$TTLkeywords. If the zone file includes
$INCLUDEkeywords, the import fails and Amazon Route 53 returns an error.
When you import the zone file, Amazon Route 53 ignores the SOA record in the zone file. Amazon Route 53 also ignores any NS records that have the same name as the hosted zone.
You can import a maximum of 1000 resource record sets. If you need to import more than 1000 records, you might be able to use the BIND to Amazon Route 53 Conversion Tool.
When the name of a resource record set in the zone file includes a trailing dot (
example.com.), the import process interprets the name as a fully qualified domain name and creates an Amazon Route 53 resource record set with that name.
When the name of a resource record set in the zone file does not include a trailing dot (
www), the import process concatenates that name with the domain name in the zone file (
example.com) and creates an Amazon Route 53 resource record set with the concatenated name (
If you use the GoDaddy export process to create a zone file, you might need to edit the zone file to add a trailing dot to MX resource record sets before you import the zone file into your hosted zone. The export process currently doesn't add a trailing dot to the fully qualified domain names of MX resource record sets, so the Amazon Route 53 import process adds the domain name to the name of the resource record set. For example, suppose you're importing resource record sets into the hosted zone
example.comand the name of an MX record in the zone file is
mail.example.com, with no trailing dot. The Amazon Route 53 import process creates an MX resource record set named
For CNAME, MX, PTR, and SRV resource record sets, this behavior also applies to the domain name that is included in the RDATA value. For example, suppose you have a zone file for
example.com. If a CNAME resource record set in the zone file (
support, without a trailing dot) has an RDATA value of
www.example.com(also without a trailing dot), the import process creates an Amazon Route 53 resource record set with the name
support.example.comthat routes traffic to
www.example.com.example.com. Before you import your zone file, review RDATA values and update as applicable.
Amazon Route 53 doesn't support exporting resource record sets to a zone file.
To create resource record sets by importing a zone file
Get a zone file from the DNS service provider that is currently servicing the domain. The process and terminology vary from one service provider to another. Refer to your provider's interface and documentation for information about exporting or saving your records in a zone file or a BIND file.
If the process isn't obvious, try asking your current DNS provider's customer support for your records list or zone file information.
Sign in to the AWS Management Console and open the Amazon Route 53 console at https://console.aws.amazon.com/route53/.
On the Hosted Zones page, create a new hosted zone:
Click Create Hosted Zone.
Enter the name of your domain and, optionally, a comment. Note that the comment can't be edited later.
On the Hosted Zones page, double-click the name of your new hosted zone.
Click Import Zone File.
In the Import Zone File pane, paste the contents of your zone file into the Zone File text box.
Depending on the number of resource record sets in your zone file, you might have to wait a few minutes for the resource record sets to be created.
If you're using another DNS service for the domain (which is common if you registered the domain with another registrar), migrate DNS service to Amazon Route 53. When that step is complete, your registrar will start to identify Amazon Route 53 as your DNS service in response to DNS queries for your domain, and the queries will start being sent to Amazon Route 53 DNS servers. (Typically, there's a day or two of delay before DNS queries start being routed to Amazon Route 53 because information about your previous DNS service is cached on DNS resolvers for that long.) For more information, see Migrating DNS Service for an Existing Domain to Amazon Route 53.