43
System Redundancy (feddit.uk)
submitted 5 months ago by Cyber@feddit.uk to c/selfhosted@lemmy.world
34 comments fedilink hide all child comments

After being home for weeks, I went away for business, the 1st night away there was a brief powercut and the firewall (on a UPS) seemed to get stuck.

So, that's no DNS, DHCP, or connectivity between wifi and LAN... All due to (admittedly aging) hardware issue.

Since then my entire home system has had issues whilst it all settles down.

It made me think about getting some redundancy into the system to handle a single failure.

So,.can you give me any insights into High Availability like CARP (for pfSense), VM failover (on Incus?), mesh wifi, Home Assistant, etc?

Of course there are going to be single points, like ISP line, etc, but seems like something to test out.

you are viewing a single comment's thread
view the rest of the comments
[-] just_another_person@lemmy.world 2 points 5 months ago
  1. Okay, so no issues there
  2. 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 2 points 5 months 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 points 5 months ago* (last edited 5 months ago)

So then as a next step, I'd set Wireshark 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 dig or nslookup.

this post was submitted on 31 Jan 2026
43 points (100.0% liked)

Selfhosted

60664 readers
909 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world