How can the domain’s zone apex for example “myzoneapexdomain com” be pointed towards an
Elastic Load Balancer?
A.
By using an AAAA record
B.
By using an A record
C.
By using an Amazon Route 53 CNAME record
D.
By using an Amazon Route 53 Alias record
Explanation:
http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-choosing-aliasnon-alias.html
D.
http://serverfault.com/questions/424253/how-does-one-point-a-domain-to-a-load-balancer-that-doesnt-have-a-stable-ip
D.(Fee from IP change)
D
A is the right answer.
Additionally, Amazon Route 53 supports the alias resource record set, which lets you map your zone apex (e.g. example.com) DNS name to your load balancer DNS name. IP addresses associated with Elastic Load Balancing can change at any time due to scaling or software updates. Amazon Route 53 responds to each request for an alias resource record set with one IP address for the load balancer. If a load balancer has more than one IP address, Elastic Load Balancing selects one of the IP addresses in a round-robin fashion and returns it to Amazon Route 53; Amazon Route 53 then responds to the request with that IP address.
Alias resource record sets are virtual records that work like CNAME records. But they differ from CNAME records in that they are not visible to resolvers. Resolvers only see the A record and the resulting IP address of the target record. As such, unlike CNAME records, alias resource record sets are available to configure a zone apex (also known as a root domain or naked domain) in a dynamic environment
D
For naked domain or zone apex always use alias record.