Why was VesperNet created?

Good question! Why is anything created? Could it perhaps be to fill a gap or a need for something? In my case, yes - both a gap and a need.

In the previous subsection, I lightly touched on the troubles of the mainstream, public internet. And this would be the core reason for the existence of the project, that and challenging myself to see how far I can take the project.
It did take quite a while to put all the pieces together, not believing in unit tests it took quite some trial and error before the basics were done and as far as I can tell - working as intended.

Now, more details about the DNS server is available further down the subsections, so let's get into why this thing was created ...

Let me list a few reasons, and they apply to me personally.

Domain control, which ones are available, what record types are available and where they point
Privacy, the zones available are the ones reachable (depending on configuration)
Telemetry, doesn't matter if applications want to send data out, if the hostname has no pointer it doesn't get sent out
Ability to spin up additional DNS servers in slave mode, in case I would ever need to, and have them sync against the master
Ability to connect to "mainstream/public" services that are confirmed safe and sound sources for the tasks at hand
No fallback to public DNS servers, as this would defeat the purpose of the entire project

Of course, at the time of creating this, I had never thought of the idea that it could also be used by other people, which is something that dawned on me as I was looking at a way to make it easy to manage zones and DNS records.
And this should also explain why vespernet.net and vespernet.org exist today.

Next subsection: Why would anyone use VesperNet?