4 ms·

It's disappointing that prior art isn't mentioned in the article. DNSMadeEasy's ANAME record does the same. I believe other providers like Route53 also call it

by zimbatm 13y ago

It's disappointing that prior art isn't mentioned in the article. DNSMadeEasy's ANAME record does the same. I believe other providers like Route53 also call it an ALIAS record. It's also good to know that GeoDNS resolution won't work as expected since the location of the resolver is going to be the DNS provider and not the client. EDIT: Actually DNSMadeEasy claims that the resolution is done locally in each of their region so the issue is somewhat mitigated.

michaelbuckbee 13y ago
I think it's about split between ALIAS and ANAME at the different providers. DNSMadeEasy -> ANAME DNSimple -> ALIAS EasyDNS -> ANAME PointDNS -> ALIAS
statico 13y ago
AWS Route 53 aliases aren't ANAME/ALIAS -- they appear to only let you point a record at an AWS address, not any arbitrary IP. (Correct me if I'm wrong.)
- colmmacc 13y ago
  Disclaimer: I work on Route 53. You can ALIAS to record sets within your own zone too, which can contain any arbitrary IP. This is useful when composing routing types (e.g. weighted plus latency). But we don't support ALIASing to record sets hosted on other DNS providers. It is possible to ALIAS to a CloudFront distribution though, and that CloudFront distribution can in turn use any arbitrary name as its origin. It's also possible to ALIAS to an S3 bucket, which can be configured with a redirect to any name of your choice. Remote DNS-level ALIAS is something that we're always considering, and we're interested in feedback. If we support it, it's unlikely our 100% availability SLA will apply, that there may be inter-operability issues with CDNs (though we recently announced our support for edns-client-subnet: http://aws.typepad.com/aws/2014/04/improved-cloudfront-performance-with-edns-client-subnet-support.html http://aws.typepad.com/aws/2014/04/improved-cloudfront-perfo...) and incompatibilities with our future DNSSEC support.
- zimbatm 13y ago
  You're probably right. I know that Route53 does support something similar but it might be AWS specific (in that it would only work with S3, CloudFront or other AWS end-points)

by zimbatm 13y ago

michaelbuckbee 13y ago

I think it's about split between ALIAS and ANAME at the different providers. DNSMadeEasy -> ANAME DNSimple -> ALIAS EasyDNS -> ANAME PointDNS -> ALIAS

statico 13y ago

AWS Route 53 aliases aren't ANAME/ALIAS -- they appear to only let you point a record at an AWS address, not any arbitrary IP. (Correct me if I'm wrong.)

colmmacc 13y ago
Disclaimer: I work on Route 53. You can ALIAS to record sets within your own zone too, which can contain any arbitrary IP. This is useful when composing routing types (e.g. weighted plus latency). But we don't support ALIASing to record sets hosted on other DNS providers. It is possible to ALIAS to a CloudFront distribution though, and that CloudFront distribution can in turn use any arbitrary name as its origin. It's also possible to ALIAS to an S3 bucket, which can be configured with a redirect to any name of your choice. Remote DNS-level ALIAS is something that we're always considering, and we're interested in feedback. If we support it, it's unlikely our 100% availability SLA will apply, that there may be inter-operability issues with CDNs (though we recently announced our support for edns-client-subnet: http://aws.typepad.com/aws/2014/04/improved-cloudfront-performance-with-edns-client-subnet-support.html http://aws.typepad.com/aws/2014/04/improved-cloudfront-perfo...) and incompatibilities with our future DNSSEC support.
zimbatm 13y ago
You're probably right. I know that Route53 does support something similar but it might be AWS specific (in that it would only work with S3, CloudFront or other AWS end-points)