by ProfDreamer on 1/28/19, 1:17 PM with 6 comments
by altmind on 1/29/19, 9:18 AM
by 3xblah on 1/29/19, 6:58 AM
you decipher the domain(s) and IP address(es) the portal uses for sign-in, then you put this info into your unbound.conf as "local-data:" or something similar.
And you are free again to ignore the DHCP provided nameservers, keeping your localhost DNS server address in resolv.conf.
"I think we can do better."
You can and I am sure you will.
What I would like to see is a localhost DNS server that runs on a mobile OS.
Perhaps you run your own wireless router between your wireless-enabled computers and the third party access point. You can send 127.x as a nameserver in DHCP but this only works if your computers can run localhost DNS, e.g., tinydns/dnscache/dqcache, nsd/unbound, etc.
by teddyh on 1/29/19, 12:29 PM
by RemarkableMan on 1/29/19, 6:39 AM