Captive Portals don't work if DNS protection is enabled.

[ponychicken]

Captive Portals mostly serve "fake" DNS in order to steer requests to the login portal.
If I connect to a wifi using this, portmaster shows a notification "Captive Portal" detected, but opening it in the browser doesn't work because the browser can't resolve the address of the portal page.

For some reason disabling the DNS protection also doesn't work (immidiately?) and the only thing that works reliably is to shutdown portmaster, login and restart the service.

Suggestion:
Add a button to the notification "Disable DNS protection for 3 minutes" to allow the user to login.

[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.