|« PreviousNext »|
|Did this page help you? Yes | No | Tell us about it...|
For each hosted zone you create, Route 53 automatically creates four name server (NS) records and one SOA record. Don't change these 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:
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 Your Registrar's Name Servers.
If you migrated an existing domain to Route 53, see Updating Your Registrar's Name Servers.
If you created a subdomain that uses Route 53 without migrating the parent domain, see Updating Your DNS Service with Name Server Records for the Subdomain.
If you migrated a subdomain to Route 53 without migrating the parent domain, see Updating Your DNS Service with Name Server Records for the Subdomain.
Some registrars only allow you to specify name servers using IP addresses; they don't allow you to specify fully qualified domain names. If your registrar requires using IP addresses, you can get the IP addresses for your name servers using the dig utility (for Mac, Unix, or Linux) or the nslookup utility (for Windows). We rarely change the IP addresses of name servers; if we need to change IP addresses, we'll notify you in advance.
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,
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
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
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, you can use the
Route 53 console. For more information, see Creating, Changing, and Deleting Resource Record Sets Using the Route 53 Console.
You can also use the
ChangeResourceRecordSets API. For more information, see
in the Amazon Route 53 API Reference.