3 ms·
The problem I have with this setup is when using networks that require you click through a captive portal. Often external DNS servers can't resolve their portal
by AdamGibbins 8y ago
The problem I have with this setup is when using networks that require you click through a captive portal. Often external DNS servers can't resolve their portals -- so you can't click through to open up to the wider internet and have to screw around flipping the DNS temp. After wondering what on earth is going on for a minute or two, as you've forgotten, again.
- ignoramous 8y agoJust curious: Wouldn't visiting sites like http://neverssl.com http://neverssl.com work? If it doesn't, then it's a good opportunity for someone to put a static-ip behind something like http://neverssl.com http://neverssl.com
- AdamGibbins 8y agoNo because often they redirect you to a DNS address that only exists in their internal DNS. And that internal DNS is often to an internal only IP, so you can't VPN all your traffic. e.g. you'll go to http://neverssl.com http://neverssl.com then get bounced to http://some.internal.net http://some.internal.net which resolves to 10.10.1.1 which finally serves the portal you have to click through.