Raphael Fiedler

We are restructuring our co debase into a mono-repo where all Portmaster components will live happily together. This issue has been moved due to this restructure.

We are restructuring our co debase into a mono-repo where all Portmaster components will live happily together. This issue has been moved due to this restructure.

We are restructuring our co debase into a mono-repo where all Portmaster components will live happily together. This issue has been moved due to this restructure.

Q9 Sadly is not super reliable, we have observed this in the past which is why we moved away from them to CF as default. https://safing.io/blog/2020/07/07/we-are-updating-portmasters-default-dns-servers/

This is a feature we have been thinking about as well, it wont happen soon, but it will probably come in the future.

there has been a similar issue reported 1.5y ago https://github.com/safing/portmaster-ui/issues/358

please do!

thank you for sharing your opinion on this. This has been the first time I heard of this use case/ complaint. We will take this into consideration for our development...

Portmaster does alert you of bypass attempts and you can always block any app from connecting to the internet

then they probably don't do their actual DNS but probably cache the answers for longer - the indication is that you see some domains but not all. also Portmaster should...