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.
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:
"Skill issue bro" /s
A 30 day DHCP lease expiration would explain OP's issue.
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.
Maybe, but I suspect it's working like this:
This would explain why Pihole appears to cause problems every month, sometimes a little longer.
Basically, no static IPs at all. Lol
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!
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.
If you're a computer geek (even a professional one) and struggle with IP addressing, you won't be having much of a career.
LMAO I know a whole bunch of people who don't know a subnet mask from a hole in their ass and they're doing just fine in their IT careers. You are overestimating the requirements for a great many corporate jobs.
Ya it’s me I’m the guy in IT who is currently confusing a subnet mask for my own ass.
Just think of it as a routing optimisation that is only relevant for ipv4 networks.
Router simple, router need to make decisions quick, quickest decision is made when can smush the subnet mask against an IP address and determine if the computer is on a local network so router can send traffic direct or is on other network so router needs to send traffic to other router
There's a difference between corporate IT and being a computer geek.
I agree that many IT careers are relatively simple support jobs.
They mentioned computer geeks which implies, to me, people who are deep into computers. In that light, if you're struggling with concepts of IP addressing then the more-complicated facets of computers and networks will preclude you from an engineering role.
Is this some kinda weird ass gatekeeping-esque computer geek thing? What you said is so wrong it's not even funny.
I'm not gate-keeping. I'm simply suggesting that IP addressing is one of the less-complicated things when it comes to computer-geekery.
Nah you're literally gatekeeping what it means to be a computer geek.maybe it's not gatekeeping per se, but you sure are wrong and look like an assI'm wrong? You're saying that IP addressing is one of the most complicated things about computers/networking?
I know reading is hard, but I'm not arguing that its a complicated task; merely that your familiarty with it does not at all reflect career prospects of a "computer geek."