VesperNet History,
section Preface

Why would anyone use VesperNet?

Well, I can't really answer for anyone else other than myself in this case. I created it, so I know for a fact that there is a use case for one or more services.

So why would anyone want to use a third party, alternative root DNS server, which doesn't even have a fallback to any "public" DNS server that allows visiting mainstream/public internet sites in case the DNS server fails to look up whatever it is you are trying to access?

To protect (privacy) and serve (configured zones)! That's why!
At least, that is my case. When using the DNS server, only the registered and configured zones are available - this means that I could potentially make any domain point to exactly whatever I want it to point to, as an example the zone apple.com is already taken and only has the time servers pointing to the "real deal", if any machine on my network wants to pass anything else to any other subdomain at apple.com, it doesn't get passed to Apple at all - since the records either don't exist, or points to 127.0.0.1 (localhost).

This means that any zone created is able to be managed, DNS records can be added, changed, removed and point to wherever they are configured to. And a zone can be dropped / transferred at any time, it all depends on how things are managed.

As a proof of concept, the following publicly accessible sites out on the mainstream internet, are also accessible via the Vesper DNS server:

Still, this only applies to my requirements, yours might differ entirely. However, it does mean that anyone could potentially do something like this ...

So as you can see, there is potential here. It is what you make it.

Next subsection: How is MacDomain tied to VesperNet?