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

Linux

13082 readers
574 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
[–] Scoopta@programming.dev 2 points 1 day ago* (last edited 1 day ago)

It's normal for the loopback con path to end in 1, each con path is unique for each interface. My guess is that if your pihole sometimes works, the IPv4 server is your pihole and the IPv6 servers are ISP provided (especially if there are 2), so they work for the internet but not your internal network. Ideally you would set your pihole's IPv6 address as your IPv6 DNS as well. Failing that, setting the IPv6 mode in your network manager UI to "Automatic, addresses only" will make it not used for DNS