How can the domain’s zone apex, for example, “myzoneapexdomain.com”, be pointed towards an Elastic Load
Balancer?
A.
By using an Amazon Route 53 Alias record
B.
By using an AAAA record
C.
By using an Amazon Route 53 CNAME record
D.
By using an A record
A
A
You can create an alias resource record set at the zone apex.
You cannot create a CNAME record at the top node of a DNS namespace, also known as the zone apex. For example, if you register the DNS name example.com, the zone apex is example.com.
Source: http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-choosing-alias-non-alias.html
a
A
A
Correct answer is B
nope. AAAA is like A, but for IPv6
A
You can use alias record sets to route DNS queries to your load balancer for the zone apex of your domain (for example, example.com).
http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/using-domain-names-with-elb.html
A is correct
A should be the correct answer
i think answer is A
using alias record for zone apex domain (example.com) and use CNAME for naked domain (non-zone apex domain) like http://www.example.com or dev.example.com
Route53 offers Alias records work like a CNAME record in that you can map one DNS name (example.com) to another ‘target’ DNS name (elb1234.elb.amazonaws.com)
A is correct without doubt. “AAAA” records are used for IPV6 IP addresses
Is it not C?
no it is not C. Certified is A
B is not correct “AAAA” records are used for IPV6 IP addresses and can’t be used for Elastic Load Balancer.
Right answer is A.
A
A
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
http://docs.aws.amazon.com/govcloud-us/latest/UserGuide/setting-up-route53-zoneapex-elb.html
A is correct
As per FAQ notes
A is correct.
“You cannot create a CNAME record at the top node of a DNS namespace, also known as the zone apex. For example, if you register the DNS name example.com, the zone apex is example.com.”
http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-choosing-alias-non-alias.html
C’mon admin. How the fuck could you put B as the answer????
By using an Amazon Route 53 Alias record