3 ms·

I use a custom resolv.conf. Really, the biggest problem is airports: some want you to go through a captive gateway, but the captive gateway's domain is not publ

I use a custom resolv.conf. Really, the biggest problem is airports: some want you to go through a captive gateway, but the captive gateway's domain is not publicly registered, so if you're using 8.8.8.8 or similar, it fails to resolve. Leads to an annoying trip to resolv.conf (well, resolvconf.conf in my case) to tell it to use the DHCP settings, run through the portal, and then flip back. (And like, is it really that hard to register your captive portal's name globally, and just let me use a global resolver to get to it? IDK if they're concerned about DNS tunneling, but this happens even on "free" WiFi (where free might mean "watch this ad", which honestly is fine w/ me.))

isostatic 8y ago
The people that run these network shave no idea what global resolving and DNS tunneling are. The people that build the systems that provide these networks likely don't know what DNS tunneling is.
JoshTriplett 8y ago
> Really, the biggest problem is airports: some want you to go through a captive gateway, but the captive gateway's domain is not publicly registered, so if you're using 8.8.8.8 or similar, it fails to resolve. Ideally, the software detecting captive portals on a network and presenting their login page should also use the network-provided DNS server solely to resolve the captive portal domain if it doesn't resolve with the preferred resolver. That would solve this case. (Also, ideally, captive portals would serve up a URL using DHCP options and not capture traffic.)
Tsiklon 8y ago
I saw another user here in this comments section reference a project which might be useful to you: https://news.ycombinator.com/item?id=19436783 https://news.ycombinator.com/item?id=19436783