Comment 24 for bug 1727237

Revision history for this message
Pete (lance321) wrote :

I too am still encountering this issue.

Since I can't resolve the webpage to the captive portal I have to manually enter its IP 1.1.1.1

Then accept the agreement. However afterwards DNS still fails to resolve web-pages.

Today I edited /etc/resolv.conf as before, adding Google DNS to show this.

nameserver 127.0.0.53
nameserver 8.8.8.8

But I noticed resolving DNS was slow, because 127.0.0.53 was failing. And after timing out it goes to the Google DNS 8.8.8.8.

After removing 127.0.0.53 in the file and only using "nameserver 8.8.8.8" everything works fine and quickly.