"Proponents of the UNIX arts-and-crafts movement just run unbound(8) on localhost. Which works reasonably well until you are behind a captive portal and you have to use the dhcp-provided nameservers until you accept the terms and conditions. So you bring out your editor again..."<p>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.<p>And you are free again to ignore the DHCP provided nameservers, keeping your localhost DNS server address in resolv.conf.<p>"I think we can do better."<p>You can and I am sure you will.<p>What I would like to see is a localhost DNS server that runs on a mobile OS.<p>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.