this post was submitted on 11 Oct 2023
85 points (85.1% liked)

Selfhosted

40023 readers
1270 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

Every month or so all my devices lose internet and the only way to connect them all back is to disconnect them from the DNS server that Pihole is running.

I set my Pihole to have a static IP but for some reason after around a month or maybe longer, it just fails. This has happened 4 times over the last while and the only fix is to essentially uninstall everything on my Pihole, disable it, and then reconfigure it from scratch again.

I’m not sure what’s going on so any help would be appreciated.

you are viewing a single comment's thread
view the rest of the comments
[–] MigratingtoLemmy@lemmy.world 43 points 1 year ago* (last edited 1 year ago) (2 children)

If you can't access your server and your router's web interface, that's a subnetting/DHCP allocation issue. Nothing to do with Pi-Hole.

For reference, there's 2 ways to allocate static addresses to devices:

  1. Define DHCP range, and configure the application to use a static address outside of the allocation pool.
  2. Give out static addresses by MAC.

"Skill issue bro" /s

[–] NaibofTabr@infosec.pub 38 points 1 year ago (2 children)

A 30 day DHCP lease expiration would explain OP's issue.

[–] fuzzy_feeling@programming.dev 19 points 1 year ago (1 children)

I vote for 60 day lease time, iirc the clients try to get a new lease when half of the time is over, so they can keep the ip.

[–] NaibofTabr@infosec.pub 9 points 1 year ago

Maybe, but I suspect it's working like this:

  • Pi boots then requests locally configured IP from DHCP server
  • DHCP server grants 30 day lease for requested IP
  • Pihole runs fine for awhile, DNS requests are properly handled
  • IP lease expires, DHCP server returns IP to available address pool but doesn't reassign it to anything yet
  • time passes
  • Random wireless device connects to router, DHCP server assigns IP to new device
  • DNS requests to Pihole fail because the IP was assigned to the recently connected wireless device

This would explain why Pihole appears to cause problems every month, sometimes a little longer.

[–] MigratingtoLemmy@lemmy.world 7 points 1 year ago

Basically, no static IPs at all. Lol

[–] PerogiBoi@lemmy.ca 18 points 1 year ago (1 children)

Definitely a skill issue haha. I’m brand new to this stuff so I’m trying to learn as fast as possible. Appreciate the help and the explanations!

[–] c0mbatbag3l@lemmy.world 10 points 1 year ago (1 children)

It's alright, most computer geeks (even professional ones) can't even figure out how IP addressing works. That's why networking is its own sub group in enterprise environments.