With a particular library's wifi, I have to temporarily disable nextdns to get to wifi landing page. How can we avoid this?
There is a library I visit with free public wifi. It's secured, but the password is displayed around the library.
When either my Android or Linux laptop are connected to nextdns, I can't get to the library wifi's landing page. I have to turn off nextdns temporarily in order to see the wifi landing page.
On Android, Settings> Connections > More Connections and Settings > Private DNS > switch from "Private DNS provider host name" to "Off".
On my linux laptop, I open a terminal and type 'nextdns stop'.
After disabling nextdns, I then can go to the library wifi's landing page, where I put a checkmark to agree to the rules, and then click/tap the Submit button. Afterwards, I can then re-enable nextdns on my phone and laptop.
But why is this necessary? On other wifi networks, even on wifi networks with their own landing page, I don't have to temporarily disable nextdns. Why do I have to this with this one library?
This article may shed some light - https://zapier.com/blog/open-wifi-login-page/
TL;DR - If you've ever added Google DNS, OpenDNS, or any other alternative DNS to your network settings, though, that may be your problem. Many public Wi-Fi networks use their DNS server to tell your computer [or mobile device] which login page to open—which doesn't work when you're using an alternative DNS server.