Comment on System Redundancy
just_another_person@lemmy.world 4 days ago- Okay, so no issues there
- DHCP handles the address assignments in your network, not DNS. DNS resolves to named host queries. If no devices got IP addresses, that’s one problem. If you couldn’t resolve public hosts like www.news.com, that’s a DNS problem. If you couldn’t resolve INTERNAL named hosts you refer to around your network, then that’s also DNS, but a different problem.
My hunch here is that you MIGHT be using a named host as your DNS resolves instead of an IP address in your network, OR, for some reason your DNS resolves doesn’t have a static address. Never use named hosts to point to network services, and all network services need a static IP, so go and check all of that.
Cyber@feddit.uk 3 days ago
Yep, all good with DHCP vs DNS… just my grammer was terrible.
Nothing was getting an IP from the DHCP, when the wifi returned…and… DNS was also not working for the few devices that still had an IP.
Sry bout the confusion there.
just_another_person@lemmy.world 3 days ago
So then as a next step, I’d set Wireguard up on one of your regularly hosts, set it to filter for DHCP traffic, confirm you’re seeing regularly advertisements first, then reboot the device that’s responsible for DHCP and make sure it resumes sending those advertisements when it comes back.
If it’s the same device handling DNS, make sure it’s also immediately returning responses after the reboot as well with
digornslookup.towerful@programming.dev 2 days ago
Wireshark*
just_another_person@lemmy.world 2 days ago
Oops, yup