3 ms·
> What's so "nasty" about using ALIAS? It's a not standard and therefore, is not a generally applicable solution. When something not standard becomes common
by Eikon 7y ago
> What's so "nasty" about using ALIAS?
It's a not standard and therefore, is not a generally applicable solution.
When something not standard becomes common practice and is expected, here comes the pain.
- XelNika 7y agoI don't really see the issue. It changes nothing from the DNS client's perspective.
- toast0 7y agoFrom the DNS client's perspective, there is a positive and a negative. Positive: since the server with an alias record actually returns an A/AAAA, a client doesn't have to contact any more servers to get the results. Negative: the servers for the CNAME target may be faster, relevant if the name is used beyond the A/AAAA TTL but sooner than the TTL would be set for a CNAME); or the servers for the target may be providing much finer targeting than is possibly by proxying.
- cbg0 7y ago> When something not standard becomes common practice and is expected, here comes the pain. I think that's the case with most popular features before they become a standard. Personally, I've used ALIAS on AWS without a hitch for years.
- SteveNuts 7y agoThe standard should be amended for the modern web then. AWS's (and I'm sure many other's) implementation of this for their various load balancing, CDN services, etc. are critical to the health of the web now.