7 ms·

Actually, most captive portals don't poison the cache (because that would break the web site you tried to load), but answers on port 80 for any and all IP addre

by 0x0 12y ago

Actually, most captive portals don't poison the cache (because that would break the web site you tried to load), but answers on port 80 for any and all IP addresses.

ferongr 12y ago
To my knowledge you can use a TTL of 0 and then you have no problems.
- 0x0 12y ago
  Wouldn't that cause problems with (a) browsers that cache dns for a little while anyways, and (b) clients arriving on the captive net but already holding a long-lived cached proper dns result?