I've got a home lab server and I can run my own DNS. I already have a pi-hole and I wanted to make a resolver also. Anyone got any setup tips?
my goal is to have a local DNS in case of DNS fuckery.
For instance - a resolver will only go to root servers, but are they likely to remain intact?
(points to tin foil hat and nods knowingly)
-edit for clarification
pi-hole with unbound is cool, and I'm considering that, but at the moment looking at DNS on windows server as a resolver not a forwarder.
Why not just hard code in your hosts file?
Unless you're trying to make this available to others... they would have to change their DNS server in their network adapter config to hard code, which is just about at the same tech level as updating their own hosts file locally. Good on you thinking about alternatives though.
that would work, not as "Easy" tho.
That said, I do have some critial IP addresses noted for just such a task.
He's probably looking for a more hands-off approach. A hosts file solution would only make sense to manage a few sites.
try this https://github.com/anudeepND/pihole-unbound
Yes! I ran unbound for a while it's neat. Then something broke and it quit working. I wasn't cool enough to fix it. It seemed to be something with the date/time.
I would consider running unbound in it's own VM to keep them separated. (My pi-hole is in a VM)
A quick alternative would be to try these servers. https://dns.watch/
If you have any trouble setting up your own, I love using this site to choose my home network DNS.
https://servers.opennic.org
I've spun up the DNS role on my windows server. I've got some familiarity with running that.
the question remains about whether there are ways to configure it to make it more bullet proof as far as suspected DNS fuckery.