Please do not run your own DNS server if you do not have the knowledge or expertise to properly secure it. It is extremely irresponsible, and the article is also irresponsible for suggesting it and not having any information about rate limiting.
I'd like to point out that google DNS among others uses anycast and are in reality composed of multiple servers geographically distributed, even if there is a single IP.
If you want to cut down on DNS-induced latency, Route 53 is a fairly good option. Their latency-routed DNS doesn't perfectly map to all geographical zones, but it works fairly well for DigitalOcean's locations.<p>I wish it was easier/cheaper to run your own anycast network...
The Powerdns geo backend as mentioned by the article is used by wikipedia among others.<p>I have some additions (e.g. Google Public DNS), see the files at <a href="https://gist.github.com/dgl/8344c3ebe405a1400e2d" rel="nofollow">https://gist.github.com/dgl/8344c3ebe405a1400e2d</a> (which also has the rsync location for the original).<p>[edit: now I read the article again I notice the author is assuming 'eu' is going to get all of EU, it won't. There need to be entries for each country.]
This is a neat article, but 'CDN' is such a broad term. This is much more a very well done proof of concept article, but fails to take into account the huge scope of a large scale CDN, and all associated quirks it comes with.