DNS redirection concepts appear in a city's captive-portal lab. Why does DNS matter for portal behavior—without needing firewall recipes?
Select an answer to reveal the explanation.
Short Explanation
The portal needs your browser to show up at the login URL—DNS tricks and HTTP interception are how many labs shove you there after you associate. It is not Bluetooth art, a WPS PIN billboard, or a way to dissolve Enterprise encryption.
Full Explanation
Captive portals commonly depend on DNS and/or HTTP interception so that client browsers are redirected to the login/accept page. That conceptual role is what OSWP-style items test. Bluetooth rewriting, publishing WPS PINs, or converting Enterprise to open auth are incorrect framings.