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?
Is your pihole server the only DNS server set? Either on your PC or router? Is network manager sometimes using a different nameserver?
How would I check that?
nmcli device show eth0Or replace eth0 with whatever interface it is. Will give you a list of all network parameters including the DNS servers. There ideally should only be one, your pihole
There is only one IP4 DNS address, however there are two IP6 DNS addresses for my ethernet interface. However, I also notice that the
GENERAL.CON-PATHends in 2, whereas I have another interfacelowhich ends in 1. Would that be a clue of anything?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
resolvectl status