Oh the Route 53 team had the same half joke as well. DNS really is a good match for fast globally distributed reads and slowish writes to a hierarchal k/v store. Lots of customers have figured this out to better (or worse) effect.

Source: Principal at AWS, worked on route 53 for a few years.

* DNS really is a good match for fast globally distributed reads and slowish writes to a hierarchal k/v store*

sounds like another good candidate for distributed TimeSeries DB or DHT type of things.

I don't get what the problem is. He used DNS as a name server, which is what it is. The only weird thing is TXT instead of CNAME.