Thanks for this great article! My two cents: > reason: do something weird and custom Oh yes please! Previous discussions on this topic: https://news.ycombina

Thanks for this great article! My two cents: > reason: do something weird and custom Oh yes please! Previous discussions on this topic: https://news.ycombinator.com/item?id=28218406 https://news.ycombinator.com/item?id=28218406 (HTML over DNS) https://news.ycombinator.com/item?id=25620411 https://news.ycombinator.com/item?id=25620411 (DNS Key Value Storage) https://news.ycombinator.com/item?id=22808121 https://news.ycombinator.com/item?id=22808121 (Wikipedia over DNS) > reason: geo DNS Please don't do this! IP addresses aren't geolocated in the common sense. The good way to get content closer to your users is to announce your IP space from your different locations. Then client ISPs can choose the best route depending on peering policy and number of hops. If your DNS lies depending on the IP who asks, you're going to have quite a bunch of people redirected to the "wrong" (far/slow from their perspective) server. The only exception i can think of is for split-horizon DNS where your local resolver advertises local IP addresses.