I thought it would be pretty cool to have DNS for my self-hosted services, so that when I'm on the home network requests go straight to my server. (I'd had some problems with unreliable DuckDNS.) I set the DNS server up on my NAS and told my wifi router to use the NAS for DNS. There was a system update on the NAS today and the update required DNS lookups in order to update the DNS server so things got totally hosed for a while.
@bellegraylane Sounds like the way to go. I'm planning to set up the same DNS on the server and configure that as backup. Need to do some investigation on what DNS server software to use.
@gooser3000 i found adguard to be easy to use. I run them in lxc containers on proxmox but also have used docker containers in the past. Depends on your setup but pihole is also recommended a lot for lightweight applications. I run DHCP on my router so the 2 DNS resolvers don’t get confused. It’s dead simple and easy to maintain.
@bellegraylane you've got 2 instances of adguard?
@gooser3000 yes. My router allows 2 entries for local DNS. It only uses one at a time, so one is redundant basically. Since the router does the DHCP, it makes the switch between then painless.
@gooser3000 hello stranger. Just wanted to share, i solved this by running 2 dns services locally and set them both up as viable options for my homelab. The router just redirects to the other one when it needs to. This solved that problem for me. It’s hard to “apt update” without dns.