Portmaster should use its own resolver for own connections.

[dhaavi]

The firewall is laid out to redirect any "rogue" DNS queries back to the Portmaster. Of course this exempts all requests the Portmaster does itself, as it is also a DNS resolver itself.

But this in turn also affects any connections that the Portmaster does by itself, which are not part of the nameserver. Currently this affects (at least) the following code sections:

portmaster/netenv/online-status.go

Line 404 in 990524e

response, err := client.Do(request)

portmaster/netenv/online-status.go

Line 440 in 990524e

ips, err := net.LookupIP(DNSTestDomain)

As well as the updating process, this time in safing/portbase:
https://github.com/safing/portbase/blob/80588d5a537470f471d1055336d0e4162fc53621/updater/fetch.go#L132

---

Fixing

This can be quite easily fixed on Linux by enabling Resolver.PreferGo and setting a custom Resolver.Dial function. The Resolver.Dial function would then return a bridge that just feeds the request data to the nameserver internally.

Unfortunately, these interfaces are currently ignored on Windows. A go proposal to change this was accepted, but not implemented yet.

[github-actions]

That was 10 years ago, I think we can close this now.

[dhaavi]

Sorry, issue was closed by misconfigured bot.