Configured DNS Servers Always Failing (IT IS NOT!)
I'll write in Human first, and the tech details are below.
I use adguard home as my home DNS. It is located at rt.my.router:853 and rt.my.router:53 and 192.168.1.1
After an hour or two of use Portmaster always complains that the DNS is failing. I switch to a different DNS server in portmaster, like cloudflare, and it works but again after a few hours complains its failing.
I like to keep my DNS blank in portmaster config and use system servers. But if I do this, after portmaster complains that DNS is failing, I can't resolve anything. So I configured portmaster to use dot://rt.my.router?ip=192.168.1.1 as the DNS in settings. And its working fine, even if portmaster is complaining the the DNS is failing. I can nslookup any domain and it loads. But portmaster says its failing and has a red icon. I restart portmaster and all of a sudden my DNS is not failing and the icon has blue dot.
WTF is portmaster's problem?
What happened: After some time DNS servers fail. Every day.
What did you expect to happen?:
DNS servers are not failing they should keep working.
How did you reproduce it?:
I'm not sure, it reproduces on its own every day.
Debug Information:
``
Paste debug information below: https://pastebin.com/mUbkLrxs
Additional logs: NJ{"Created":1746166930,"Modified":1746166930,"Expires":1748758930,"Deleted":0}S executing app2/portmaster-app version 1.6.33 on linux amd64
(portmaster-app_v1-6-33:12432): Gtk-WARNING **: 23:22:10.754: Theme parsing error: gtk-dark.css:2560:51: Using one color stop with linear-gradient() is deprecated.
(portmaster-app_v1-6-33:12432): libayatana-appindicator-WARNING **: 23:22:10.823: libayatana-appindicator is deprecated. Please use libayatana-appindicator-glib in newly written code.
(portmaster-app_v1-6-33:12432): Gtk-WARNING **: 23:22:11.180: Theme parsing error: gtk-dark.css:2560:51: Using one color stop with linear-gradient() is deprecated.
(WebKitWebProcess:12502): Gtk-WARNING **: 23:22:11.278: Theme parsing error: gtk-dark.css:2560:51: Using one color stop with linear-gradient() is deprecated.
(WebKitWebProcess:12506): Gtk-WARNING **: 23:22:11.395: Theme parsing error: gtk-dark.css:2560:51: Using one color stop with linear-gradient() is deprecated.
This is a continuation of issue #1608
editing /etc/dnsmasq.conf and on line 134 removing # from #bind-interface to make it say bind-interface does not resolve the matter
I have done due diligence in ensuring it is not any other facet of my network DNS failing
As it stands, restarting portmaster makes the DNS work
What's interesting, I can see in Adguard Home that my queries are being looked up and returned correctly
But nslookup returns NXDOMAIN
Well, Adguard is configured to return REFUSED not NXDOMAIN, so where is portmaster getting NXDOMAIN from?
Changed to BETA version... now it keeps telling me every few minutes:
Detected Compatibility Issue
Portmaster detected that something is interfering with its operation. This could be a VPN, an Anti-Virus or another network protection software. Please check if you are running an incompatible VPN client or software and disable it. If that does not help, get support here.
I don't have anything else running on the computer.
Some more info...
dnsmasq is not a factor. With service stopped this issue persists.
DNS Server is irrelevant. I like to use my router as server. But even if I select one of the DNS Servers from quick settings, it stops working after some time.
Behavior can be explained as such:
Local DNS Stops resolving. I open terminal ping or nslookup anywebsite.com, it cannot resolve. I shut down portmaster. It begins to resolve.
Or,
Whichever DNS stops resolving I open terminal ping or nslookup anywebsite.com, it cannot resolve I change DNS server to a different DNS server All of a sudden it can resolve
I am running the into the same issue, you cannot save an DNS that is not DoT and DoH, I also have a local AdGuardHome server, so I am also using DNS in the clear on my local network. The issue is that you cannot save that config, I do not see the UI allowing it, then everything fails until I shutdown portmaster.
Would be great if LAN IP's would be allowed. I understand this breaks security in a sense, but it could be done visually with a warning to prompt the user, because in this case it now breaks everything. I have extensive caching and ad blocking and now this program will sidestep all of that. Defeating the purpose of having a local DNS that blocks known ads domains.
I am running the into the same issue, you cannot save an DNS that is not DoT and DoH, I also have a local AdGuardHome server, so I am also using DNS in the clear on my local network. The issue is that you cannot save that config, I do not see the UI allowing it, then everything fails until I shutdown portmaster.
Would be great if LAN IP's would be allowed. I understand this breaks security in a sense, but it could be done visually with a warning to prompt the user, because in this case it now breaks everything. I have extensive caching and ad blocking and now this program will sidestep all of that. Defeating the purpose of having a local DNS that blocks known ads domains.
I am also running a AdGuard Home server with the same issues where it says it failed resolving for some odd reason?
Portmaster goes to my AdGuard IP with regular unencrypted DNS and AdGuard uses upstream TLS.
This issue happens multiple times, for a few minutes and then it starts randomly working again.
Same here, Adguard unencrypted DNS.
Same issue here. What I noticed is that it immediately starts working again when I add or delete a new DNS server entry.
So in addition to an entry "dns://