)]}'
{"specs/liberty/alias-records.rst":[{"author":{"_account_id":8098,"name":"Joe McBride","email":"jmcbride@rackspace.com","username":"mejoe"},"change_message_id":"9cde985f8b228d74a96b8e30c16455b98a747bc6","unresolved":false,"context_lines":[{"line_number":86,"context_line":""},{"line_number":87,"context_line":"The interval at which ALIAS records are flattened will be configurable,"},{"line_number":88,"context_line":"defaulting to 1800 seconds (30 minutes)."},{"line_number":89,"context_line":""},{"line_number":90,"context_line":"Finally, a new RPC method will be implemented to trigger immediate ALIAS"},{"line_number":91,"context_line":"flattening for a specific Zone, allowing for newly created ALIAS RR\u0027s to be"},{"line_number":92,"context_line":"usable before the first periodic interval is hit."}],"source_content_type":"text/x-rst","patch_set":1,"id":"3afb71cf_b769ee8d","line":89,"updated":"2015-06-05 15:47:09.000000000","message":"\"Flattening\" of records will be problematic for some CDN providers.  For example, I pinged a1907.dscg.akamai.net from different regions and received a different IP for each region:\n\nSYD: \n- 14.200.100.81\n- 14.200.100.75\n\nDFW\n- 204.0.5.35\n- 204.0.5.42\n\nHKG\n- 42.99.128.147\n- 42.99.128.145\n\nIn this case, Akamai seems to be using some algorithm to route a user to the closest location/IP. If Designate \"flattens\" the record, it will only serve the IP it received, which would likely be near it\u0027s deployment location.  This would totally invalidate using a CDN with this service, which is a cited use case.","commit_id":"54b2e1d59cec8296e4fd5837a91203f09f0e5d6a"},{"author":{"_account_id":741,"name":"Kiall Mac Innes","email":"kiall@macinnes.ie","username":"kiall"},"change_message_id":"a95f3dc84a0a72cde1b9721685676983703a4de3","unresolved":false,"context_lines":[{"line_number":86,"context_line":""},{"line_number":87,"context_line":"The interval at which ALIAS records are flattened will be configurable,"},{"line_number":88,"context_line":"defaulting to 1800 seconds (30 minutes)."},{"line_number":89,"context_line":""},{"line_number":90,"context_line":"Finally, a new RPC method will be implemented to trigger immediate ALIAS"},{"line_number":91,"context_line":"flattening for a specific Zone, allowing for newly created ALIAS RR\u0027s to be"},{"line_number":92,"context_line":"usable before the first periodic interval is hit."}],"source_content_type":"text/x-rst","patch_set":1,"id":"3afb71cf_b542ea3c","line":89,"in_reply_to":"3afb71cf_b769ee8d","updated":"2015-06-07 14:58:46.000000000","message":"Yep, this is a problem for any non-live implementation. And - Even then - If the CDN doesn\u0027t support EDNS client subnet, you\u0027ll still get the closest result to the nameserver.\n\nMaybe we should use this feature as the excuse to to do \"pluggable RR types\".. Flattened ALIAS being one plugin, PowerDNS live ALIAS being another. This clearly doesn\u0027t help BIND - But, BIND doesn\u0027t support \"live\" ALIAS\u0027s so there\u0027s nothing we can do there other than go implement support in BIND :(","commit_id":"54b2e1d59cec8296e4fd5837a91203f09f0e5d6a"}]}