Monday, December 15, 2014<\/p>\n
\n Recently the Google Public DNS team, in collaboration with Akamai, reached an important milestone:
\n Google Public DNS now propagates client location information to Akamai nameservers. This effort
\n significantly improves the accuracy of approximately 30% of the location-sensitive DNS responses
\n returned by Google Public DNS. In other words, client requests to Akamai hosted content can be
\n routed to closer servers with lower latency and greater data transfer throughput. Overall, Google
\n Public DNS resolvers serve 400 billion responses per day and more than 50% of them are
\n location-sensitive.\n<\/p>\n
\n DNS is often used by Content Distribution Networks (CDNs) such as Akamai to achieve location-based
\n load balancing by constructing responses based on clients’ IP addresses. However, CDNs usually see
\n the DNS resolvers’ IP address instead of the actual clients’ and are therefore forced to assume
\n that the resolvers are close to the clients. Unfortunately, the assumption is not always true.
\n Many resolvers, especially those open to the Internet at large, are not deployed at every single
\n local network.\n<\/p>\n
\n To solve this issue, a group of DNS and content providers, including Google, \n This solution requires that both resolvers and CDNs adopt the new DNS extension. Google Public \n For more information about Google Public DNS, please visit Monday, December 15, 2014 Recently the Google Public DNS team, in collaboration with Akamai, reached an important milestone: Google Public DNS now propagates client location information to Akamai nameservers. This effort significantly improves the accuracy of approximately 30% of the location-sensitive DNS responses returned by Google Public DNS. In other words, client requests to Akamai […]<\/p>\n","protected":false},"menu_order":83581,"template":"","meta":{"footnotes":""},"ar_kb_kategori":[665],"ar_kb_etiket":[],"class_list":["post-24860","ar_kb","type-ar_kb","status-publish","has-post-thumbnail","hentry","ar_kb_kategori-blog"],"_links":{"self":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/24860","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb"}],"about":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/types\/ar_kb"}],"version-history":[{"count":0,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/24860\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media\/27047"}],"wp:attachment":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media?parent=24860"}],"wp:term":[{"taxonomy":"ar_kb_kategori","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_kategori?post=24860"},{"taxonomy":"ar_kb_etiket","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_etiket?post=24860"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n proposed an approach<\/a>
\n to allow resolvers to forward the client’s subnet to CDN nameservers in an extension field in the
\n DNS request. The subnet is a portion of the client’s IP address, truncated to preserve privacy.
\n The approach is officially named
\n edns-client-subnet<\/span><\/a>
\n or ECS.\n<\/p>\n
\n DNS resolvers automatically probe to discover ECS-aware nameservers and have observed the
\n footprint of ECS support from CDNs expanding steadily over the past years. By now, more than 4000
\n nameservers from approximately 300 content providers support ECS. The Google-Akamai collaboration
\n marks a significant milestone in our ongoing efforts to ensure DNS contributes to keeping the
\n Internet fast. We encourage more CDNs to join us by supporting the ECS option.\n<\/p>\n
\n our website<\/a>. For CDN operators, please also visit
\n “A Faster Internet<\/a>” for more
\n technical details.\n<\/p>\n