Also, the fees for updating DNS records go straight to the validators (people running the nodes) and this list of validators can change over time so it's not a fixed set of entities; yet whoever they are, they always have a substantial personal stake in the reliability of the project.
You don't need to throttle data creation, with PoS, the price of the token goes up with market demand for it. You just need to make the token the main mechanism for payment for purchasing domains and doing zone file updates. This coupling can be built into the code. Many projects have done similar things. E.g. FileCoin coupling token price to storage space.
...Problem with FileCoin is that while it's good for high-read, low-write scenarios (like DNS), it's not so good if everyone needs to update files frequently as update costs become prohibitively expensive. I guess FileCoin could be great for CDN use case.