PiHole Dnscrypt + Mullvald + Portmaster : Unresolvable dns requests

[Kylvan-8]

What happened:

I'm currently using PiHole to manage my dns request with dnscrypt plugin.
I've never had issue while using my PiHole and Mullvald with custom dns option for any protocols etc..

So i've followed strictly this guide : https://wiki.safing.io/de/Portmaster/App/Compatibility/Software/MullvadVPN

Set up my local PiHole IP address in the dns server as dns://piholeIPaddress format
And now i'm not able to resolve dns requests anymore from my pc client.
I've tried to change (as recommended on discord) the Retry Failing DNS Servers and now i get the message Device is offline while Portmaster is still monitoring my network activity.

What did you expect to happen?:

To resolve dns requests through my pihole and still use Portmaster to block unwanted IP requests.

How did you reproduce it?:

As stated above.

Debug Information:

Platform: Microsoft Windows 11 IoT Enterprise LTSC 2024 10.0.26100 Build 26100

System: Microsoft Windows 11 IoT Enterprise LTSC 2024 windows (Standalone Workstation) 10.0.26100 Build 26100
Kernel: 10.0.26100 Build 26100 x86_64

No Module Error

Unexpected Logs

241217 02:25:02.695 er/resolve:460 > WARN 542 resolver: query to dns://PiHoleIPAddress:53#config failed: read udp PCClient:29101->PiHoleIPAddress:53: i/o timeout
241217 02:25:02.695 ine-status:561 > WARN 544 netenv: dns query check failed: all 1 query-compliant resolvers failed, last error: read udp PCClient:29101->PiHoleIPAddress:53: i/o timeout
241217 02:25:15.696 er/resolve:460 > WARN 546 resolver: query to dns://PiHoleIPAddress:53#config failed: read udp PCClient:19139->PiHoleIPAddress:53: i/o timeout
241217 02:25:15.696 ine-status:561 > WARN 548 netenv: dns query check failed: all 1 query-compliant resolvers failed, last error: read udp PCClient:19139->PiHoleIPAddress:53: i/o timeout
241217 02:25:28.701 er/resolve:460 > WARN 550 resolver: query to dns://PiHoleIPAddress:53#config failed: read udp PCClient:17775->PiHoleIPAddress:53: i/o timeout
241217 02:25:28.701 ine-status:561 > WARN 552 netenv: dns query check failed: all 1 query-compliant resolvers failed, last error: read udp PCClient:17775->PiHoleIPAddress:53: i/o timeout
241217 02:25:41.705 er/resolve:460 > WARN 554 resolver: query to dns://PiHoleIPAddress:53#config failed: read udp PCClient:50715->PiHoleIPAddress:53: i/o timeout
241217 02:25:41.705 ine-status:561 > WARN 556 netenv: dns query check failed: all 1 query-compliant resolvers failed, last error: read udp PCClient:50715->PiHoleIPAddress:53: i/o timeout
241217 02:25:54.709 er/resolve:460 > WARN 558 resolver: query to dns://PiHoleIPAddress:53#config failed: read udp PCClient:36110->PiHoleIPAddress:53: i/o timeout
241217 02:25:54.709 ine-status:561 > WARN 560 netenv: dns query check failed: all 1 query-compliant resolvers failed, last error: read udp PCClient:36110->PiHoleIPAddress:53: i/o timeout
241217 02:26:03.502 CURRENT TIME

Status: Offline

OnlineStatus:          Offline
CaptivePortal:         

SPN: disabled (module disabled)

HomeHubID:    
HomeHubName:  
HomeHubIP:    
Transport:    
---
Client:       true
PublicHub:    false
HubHasIPv4:   false
HubHasIPv6:   false

Resolvers: 1/1

PiHoleIPAddress (dns://PiHoleIPAddress:53#config)
  dns://PiHoleIPAddress:53#config
  Failing: false

Config: 11

dns/nameserverRetryRate: 10
dns/nameservers: [redacted]
dns/noAssignedNameservers: false
dns/useStaleCache: false
filter/blockInbound: true
filter/endpoints: [redacted]
filter/lists: [TRAC MAL DECEP BAD BIGT UNBREAK]
filter/preventBypassing: false
filter/serviceEndpoints: [redacted]
spn/enable: false
spn/use: false

Additional logs can be found here:
Same as errors in the general debug info

[github-actions]

Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:

• 🗣️ Our community on Discord is super helpful and active. We also have an AI-enabled support bot that knows Portmaster well and can give you immediate help.
• 📖 The Wiki answers all common questions and has many important details. If you can't find an answer there, let us know, so we can add anything that's missing.

[github-actions]

Hey @Kylvan-8, thank you for raising this issue with us.

After a first review we noticed that we will require the Debug Info for further investigation. However, you haven't supplied any Debug Info in your report.

Please collect Debug Info from Portmaster while the reported issue is present.

[Raphty]

The debug info is not complete, you mentioned mullvad, it might be something else as well.

Sadly the compatibility with mullvad has been up and down over the years, as you can see in many issues here.