Content delivery networks impacted by public DNS?

[David M]

Given there are a number of CDN that are using DNS to redirect traffic
based on geo-location and load, aren't we going to see some
significant issues?

I appreciate the Google DNS service is using anycast addresses 8.8.8.8
etc, however I'm curious as to what happens from here. Will there be
an internal hierarchy of Google DNS servers, will we see queries
originate from the anycast addresses, or are different addresses used?

Consider this example, today you are with ISP1, and you would
typically use the ISP1 DNS resolvers for your broadband connection.
When you access a website, say www.domain.com you perform a DNS query
to your ISP1 resolvers, which in turn query the NS for domain.com. The
domain.com NS can see the connection coming from ISP1 DNS servers and
make a pretty good guess at where you the user are.
In public DNS this is more problematic, geo-locating content delivery
networks (Akamai for example) are going to have a really hard time
telling where you are, if they see all queries for ISP1, and ISP2
coming from the Google DNS servers.

While I am all for the idea of improving DNS services, it is important
to discuss the impacts to the community. Perhaps a bit more insight
into how the Google DNS servers will resolve client queries can help
CDN developers and operators.

Thoughts?

[Paul S. R. Chisholm]

David, thanks for your concern. Content distribution networks and open
resolvers (or any resolvers geographically distant from users) do have
issues. This has been discussed before in this forum; for example:

http://groups.google.com/group/public-dns-discuss/msg/1bb9feb0922ff585

On Dec 4, 12:10 pm, Prem Ramaswami <pr...@google.com> wrote:
> All public resolvers will since the DNS protocol uses the resolver IP.
>
> We are continuing to work with other companies and individuals on possible
> solutions.
>
> Thanks!
>
> --
> =======================
> Prem Ramaswami
> Product Manager - Google
> http://www.google.co.in/internetbus
> =======================

This work is still continuing. --PSRC