NOTICE: Due to a lapse in annual appropriations, most of this website is not being updated. Learn more.
Form submissions will still be accepted but will not receive responses at this time. Sections of this site for programs using non-appropriated funds (such as NVLAP) or those that are excepted from the shutdown (such as CHIPS and NVD) will continue to be updated.
An official website of the United States government
Here’s how you know
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock (
) or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.
DNS-based server redirecting has been realized as the most popular way to deploy CDNs. However, with the increasing use of remote DNS, DNS-based CDNs faces a great challenge in performance degradation. To address this challenging issue, encouraging progress has been made from both industry and research communities. In this article, the state-of-art solutions for the remote DNS problem are discussed at first. Next, the privacy concerns about DNS-based CDN, including client location as well as redirection privacy, are identified and a representative solution is summarized. At last, comparisons for prior work under the different measures are conducted. We believe that this survey will shed lights on the application of DNS-based CDNs and it is expected to provide design guidelines to the CDN service providers.
Wang, Z.
and Rose, S.
(2018),
Evolution and Challenges of DNS-Based CDNs, Digital Communications and Networks, [online], https://doi.org/10.1016/j.dcan.2017.07.005
(Accessed October 10, 2025)