And I see this as one. It does possess the potential and near certainty of improving the results of CDN targeting for users who use non-local DNS servers for resolution. Many of these third party non local DNS providers are thriving because so many 'service providers' are so utterly inept at delivering the net keystone component, DNS resolution. I don't now, and have not for many years rely on provider DNS servers for exactly this reason. This will help the third party DNS providers enable CDNs to do a better job. It will allow a better hit rate for sites that try to geotarget (we do). It has some very interesting potential side effects in the war on spam, botnets, hijacked IP blocks, etc which I won't get into or forget. Does it reduce fundamental anonymity somewhere? Maybe, but really I think that impact is lost if you actually make the connection to the A record you are given, I mean really, if your DNS request was tagged from 172.16.254.0/24, and then you connect to my server from 172.16.254.5, ah where is the foul? (RFC 1918 example IP addresses used to protect the innocent IP addresses). It does mean that I can tell you 'piss off mate' at the DNS level rather that doing it at the network service level which has some potential usefulness/humor value/abuseability but really only if you actually use a DNS server that has the extensions. Could some genius ISP think, "oh, we will railroad you into using this" ? Perhaps, but that will only captivate those who choose to be captivated, PAT, vpns, tunneling, anybody who wants to will drill a walk right through sized hole in that in short order. So, at the end of the day, personally, while I am a bit miffed about some of Google's other recent activity (the broken on off switch on the toolbar tracking and other BigBroMo activity comes to mind) I think this does have some strong technical merits and it's ability to be used in an evil manner is very limited in my opinion.