“When i see an anxious person, I ask myself, what do they want? For if a person wasn’t wanting something outside of their own control, why would they be stricken by anxiety?” — EPICTETUS
Route 53 is a highly available and scalable Domain Name System (DNS) by Amazon.
DNS is a service that translate human readable domain name to IP add (IPv4–32 bits & IPv6–128 bits). This allow devices to communicate with each other over the network.
ELB does not have a pre-defined IPv4 address and we resolve to them using a DNS name.
Access controls to Route 53 can be managed using AWS IAM service to control users who are allowed to make changes to DNS records.
Query logging is available using CloudWatch. CloudTrail available fto record and log API call history for Route 53.
Top level domain names are controlled by IANA (Internet Assigned Numbers Authority)
- Top level: .com, .gov, .com.sg, .gov.sg
- Second level: .com.sg, .gov.sg
DNS record types supported by Route 53:
1.Start of Authority (SOA) record: Every DNS record begins with an SOA record. It contains information such as:
- Name of server that supplied data for the zone
- Administrator of the zone
- Current version of the data file
- Default number of seconds for the time-to-live (TTL) file on resource records (TTL: the length a DNS record is cached on the resolving server/ users local PC in seconds. The lower the TTL, the faster changes in DNS propagates throughout the internet. Usually 48 hours)
2.Name Server (NS) record: Used by top level domain servers to direct traffic to content DNS server which contains authoritative DNS records.
3.Address (A) record: Translate name of the domain to an IP address
4.Canonical Name (CNAME) record: Resolve one domain name to another. eg mapping domain name for mobile website. http://m.url.com and http://mobile.url.com. CNAME cannot be used for naked domain name (without the www or mobile in domain name)
5.Alias record: Create alias records to route traffic to selected AWS resources such as ELB, CloudFront, Elastic Beanstalk, API gateway, VPC interface endpoints and S3 buckets configured as websites. They work like CNAME record but is able to map one DNS to another target DNS name (preferred over CNAME).
