Reputation
Top tag
Next privilege 200 Rep.
See reduced ads
Badges
1 6
Newest
 Tumbleweed
Impact
~8k people reached

  • 0 posts edited
  • 0 helpful flags
  • 0 votes cast
Jun
29
comment Why are Amazon EC2 Elastic IPs encouraged to be used with a CNAME rather than an “A” record?
turns out it was a configuration error on the server. Thanks for your help. I did leave it as a CNAME to have the benefit of having Amazon control the layer of indirection.
Feb
6
comment Why are Amazon EC2 Elastic IPs encouraged to be used with a CNAME rather than an “A” record?
Thanks for the answer. I do have an Elastic IP, however, Amazon's documentation says to not have A records point to that elastic IP, but to use a CNAME instead. For some reason, when I setup a CNAME to point to "ec2-111-111-111-111.compute-1.amazonaws.com." it still resolves to ec2-111-111-111-111.compute-1.amazonaws.com in the address bar, rather than just staying ec2.example.com.
Feb
5
comment Why are Amazon EC2 Elastic IPs encouraged to be used with a CNAME rather than an “A” record?
Better question, why is it resolving to the different URL then? I thought it was because it was a CNAME