Yes, been doing so since I bought my personal domain circa 1999.

Stack: named - on Slackware (various versions over the years as the computer was upgraded).

Mail-In-a-Box (MIAB)[1] comes with a built in nameserver. I think you may use it as a standalone DNS even for the domain names whose email is not managed by MIAB. Not sure about any benefit of doing it this way though.

[1] https://mailinabox.email

No, it's the last thing I would care about self-hosting. I don't see any benefit over configuring some DNS service with terraform.

I've used PowerDNS at some point with MySQL backend. Rock stable with easy to replicate data.

No, but I'm curious what would motivate you to consider it?

I roll my own and have done so since the late 1990s.

It's bind[0] on GNU/Linux, which has served me well.

I also use a local recursive resolver rather than my ISP/Google/Cloudflare/etc., which works nicely and isn't beholden to anyone but the root servers[1]

[0] https://en.wikipedia.org/wiki/BIND

[1] https://en.wikipedia.org/wiki/Root_name_server

Edit: Fixed reference numbering.

Yes, commercial dns hardware in hot standby. 10gbit links 1 hop from tier 1 routing. In 2 rather quality datacenters.

honestly, long gone are the days of the network solutions monopoly and shitty service. If I had the power I would move everything to a registrar to host. Alas, out of my control.

Of course I run my DNS servers, actually I run powerdns and my custom pipe backend with very advanced geodns capabilities, aliases, load balancing, health checks, etc.

This is private backend, not open source.

It cost me four virtual machines, approximately $6/month each vm, but it is well worth it. And a bit of development time for the backend, but it runs for years, stable.