badnano.blogg.se - Mozilla vpn

In particular with Scenario 3, if somebody was successfully on a given Custom DNS server, I don’t know why we would want to assume that the fallback is Standard, instead of whichever (valid) Custom DNS server they were on (which they themselves set).Ĭc' Andrea Marchesini to make sure we all align on this. You are in ‘Custom DNS' with ‘1.1.1.1’ (valid), you place ‘foobar’ (invalid) in the text field and exit the view → when you come back to you should see ‘Custom DNS’ with ‘1.1.1.1’ as it was the last valid entry.You are in ‘Standard DNS', switch to Custom, place ‘1.1.1.1’ (valid) in the text field, then change it to ‘foobar’ (invalid) and exit the view → when you come back to you should see ‘Standard DNS’ as it was the last valid entry (since ‘foobar’ was never applied as it failed validation).

The toggle turns green when enabled and a message indicating that VPN is on will appear on the main screen to let you know your connection is secure and private. Select the toggle under Turn on to protect your privacy.

You are in ‘Standard DNS', switch to Custom, place ‘foobar’ (invalid) in the text field and exit the view → when you come back to you should see ‘Standard DNS’ as it was the last valid entry. To turn the VPN on, do the following: Open the Mozilla VPN app.

What I propose is that we revert back to the last valid applied DNS. We are discussing this across many bugs at this point.