I'm building a DNS service at the moment. Geo-aware DNS won't be a launch feature but it is something I intend to add in the future. The implementation I'm looking at doing will allow for returning different record data based on country-code (as determined by Maxmind GeoIP) and will be configurable via both a web interface and JSON over HTTP API. I'd be interested to know what features you'd look for in a Geo-aware DNS service and what you'd expect to pay — if you could drop me note (see profile) it'd be much appreciated.

Good question. Really, it depends on the TTL... but that's not very helpful.

I checked the stats for one of our embedded apps, and I'm seeing a ratio of ~11 pageviews to 1 DNS query. That's with a 7.5 minute TTL. Clearly, your mileage may vary.

I'd be interested to know the ratio for a destination site with a longer TTL.