One use case that i can think of is split DNS, when you'd like to return different data to different clients, about which i wrote on my blog: https://blog.kroni

One use case that i can think of is split DNS, when you'd like to return different data to different clients, about which i wrote on my blog: https://blog.kronis.dev/tutorials/how-to-run-a-split-dns-server https://blog.kronis.dev/tutorials/how-to-run-a-split-dns-ser... That said, outside of serious enterprise settings, you can do all sorts of things without hosting your own DNS servers - even odd ones, like making records on public DNS servers for your internal network. Sometimes using a dynamic DNS client (e.g. ddclient) is actually easier than caring about setting static IP addresses (if you just want to let DHCP handle everything), when you don't care about that sort of data being exposed. Of course, that's not to say that people should actually do stuff like that, just that they can. On a more practical note, if you use the DNS servers of someone like NameCheap or GoDaddy, you might run into limits for how many records for a domain you can create. For example, NameCheap allows up to 150 records (https://www.namecheap.com/support/knowledgebase/article.aspx/10058/10/namecheap-dns-limits/ https://www.namecheap.com/support/knowledgebase/article.aspx...).