|
|
|
|
|
by rob-olmos
1907 days ago
|
|
If each Route 53 POP is already close to the querying DNS client, then things like geo routing with cached answers might just work well enough in most cases? With each POP having its own cache. Auto-refreshing the popular records in the background before the TTL expires to help smooth over any temporary issues? Other big name DNS providers have ALIAS type records. I imagine according to the SLA, AWS Route 53 is still "available", even if it can't resolve a "target address record" (as the ANAME draft calls them) but Route 53 is still able to respond. |
|