this post was submitted on 31 Mar 2026
36 points (100.0% liked)

Linux

13082 readers
919 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago
MODERATORS
Ategon@programming.dev
anzo@programming.dev
dwraf_of_ignorance@programming.dev
36
Weird networking issue, seeking help (piefed.ca)
submitted 3 days ago by iamthetot@piefed.ca to c/linux@programming.dev
21 comments fedilink hide all child comments
 

I run CachyOS on my desktop. I host Homepage for myself on a home server. This is reached at home.mydomain.tld. Pihole on my local network catches that request and points it at my local nginx, which reverse proxies me to the homepage.

Now, I set this all up a while back and it all worked totally fine for several weeks. Then, about a week or so ago, for some reason almost every, but not every time I boot my PC, home.mydomain.tld gives me a "cannot be reached" error in my browser... until I run systemctl restart NetworkManager and then it works completely normally.

Can anyone help me troubleshoot why oh why that would suddenly be a thing? Does anyone have suggestions of a way I can troubleshoot a permanent fix to this so that I don't have to restart NetworkManager almost every boot?

you are viewing a single comment's thread
view the rest of the comments
[–] MangoPenguin@piefed.social 2 points 2 days ago* (last edited 2 days ago) (1 children)

I don't think it's a problem with PiHole realistically, it sounds more like for some reason your DNS requests are not getting to PiHole.

[–] iamthetot@piefed.ca 2 points 2 days ago (1 children)

Can confirm, when this happens my requests from desktop are not getting to pi-hole. Works from my phone without issue.

[–] MangoPenguin@piefed.social 2 points 2 days ago

Nice, narrowing it down!

Next thing I would check is your configured DNS servers on the desktop, it needs to have only the pihole IP, if it has any other servers configured that is likely the issue.

Also worth pinging the pihole IP next time it's not working, to check if it's actually a networking issue instead of a DNS issue.