[Dnssec-trigger] dnssec-trigger at Hotel hotspot in Vienna
paul at xelerance.com
Tue Sep 20 18:12:54 UTC 2011
On Tue, 20 Sep 2011, Carsten Strotmann (private) wrote:
> The hotel has an captive portal WLAN. DNSSEC was working using the
> WLAN DNS (from DHCP), so DNSSEC-Trigger configured the use of the
> Unbound DNS on localhost. However the captive portal login page was
> only available when using the DHCP supplied DNS Servers (non-delegated
> private DNS name for the portal page). So the only way to do anything
> else then DNS (I know, who needs that :) ) did not work in this setup.
> Not sure how this can be solved, maybe by having DNSSEC-trigger to
A quick fix might be to hit "184.108.40.206" in your browser. A lot of captive
portals then grab the stream into the captive portal.
I thought DNS redirect portals were dying out in favour of ip port 80/443
grabbing portals, but I guess there might be a lot of cruft out there.
More information about the dnssec-trigger