| « PreviousNext » | |
   | Did this page help you? Yes | No | Tell us about it... |
NS and SOA Records that Route 53 Creates for a Hosted Zone
For each hosted zone you create, Route 53 automatically creates four name server (NS) records and one SOA record. Don't change these records.
Name Server (NS) Records
The name server records that Route 53 automatically creates at the apex of your hosted zone are the authoritative name servers for your zone. You should not modify these records or add more name servers. The names of Route 53 name servers look like this:
ns-2048.awsdns-64.com
ns-2049.awsdns-65.net
ns-2050.awsdns-66.org
ns-2051.awsdns-67.co.uk
After you create a hosted zone, update your registrar's or your DNS service's name server records, as applicable, to refer to the Route 53 name servers:
If you created a domain that uses Route 53 as the DNS service, see Updating the Registrar's Name Servers.
If you migrated an existing domain to Route 53, see Updating Your DNS Service's Name Server Records.
If you created a subdomain that uses Route 53 without migrating the parent domain, see Delegating Responsibility for the Subdomain to Route 53.
If you migrated a subdomain to Route 53 without migrating the parent domain, see Delegating Responsibility for the Subdomain to Route 53.
The Start of Authority (SOA) Record
The SOA record identifies the base DNS information about the domain, for example:
ns-2048.awsdns-64.net. hostmaster.example.com. 1 7200 900 1209600 86400
The elements of the SOA record include:
The host that created the SOA record, for example,
ns-2048.awsdns-64.net.The email address of the administrator in a format with the
@symbol replaced by a period, for example,hostmaster.example.com. The default value is an amazon.com email address that is not monitored.A revision number to increment when you change the zone file and distribute changes to secondary DNS servers, for example
1.A refresh time in seconds that secondary DNS servers wait before querying the primary DNS server's SOA record to check for changes, for example
7200.The retry interval in seconds that a secondary server waits before retrying a failed zone transfer, for example
900(15 minutes). Normally, the retry time is less than the refresh time.The expire time in seconds that a secondary server will keep trying to complete a zone transfer, for example
1209600(two weeks). If this time expires prior to a successful zone transfer, the secondary server will expire its zone file. This means that the secondary server will stop answering queries because it considers its data too old to be reliable.The minimum time to live (TTL). This value helps define the length of time that an NXDOMAIN result, which indicates that a domain does not exist, should be cached by a DNS resolver. Caching this negative result is referred to as negative caching. The duration of negative caching is the lesser of the SOA record's TTL or the value of the minimum TTL field. The default minimum TTL on Route 53 SOA records is 900 seconds. To change the TTL for resource record sets, including SOA resource record sets, use the
ChangeResourceRecordSetsAPI. For more information, see ChangeResourceRecordSets in the Amazon Route 53 API Reference.
