[Dnssec-trigger] dnssec-trigger at Hotel hotspot in Vienna
paul at xelerance.com
Tue Sep 20 20:17:23 UTC 2011
>> The real question is should dnssec-trigger get involved here or
>> not. Ideally, the OS or browser is going to do the portal
>> dnssec-trigger could decide to reprobe every 5 seconds if it sees
>> this "portal" indicator? eg remain more aggressive while on a
>> suspected landing page that hopefully soon will open up auth DNS.
> dnssec-trigger thinks it succeeds, effectively disabling MacOS X
> portal detection, so if dnssec-trigger is executed before the portal
> detection, the system fails. Sometimes dnssec-trigger is running after
> the portal-detection, then it works.
So if dnssec-trigger also GET's http://www.apple.com/library/test/success.html,
it could leave unbound in 127.0.0.127 state while waiting on the portal
page to become available. Once it does, do the DNS probe?
More information about the dnssec-trigger