Dynamic Airline/Captive Portal Domain List
launched
Bailey Taylor
Fabio and the team at Tivly have expressed interest in a dynamic, auto-maintained list of airline and captive portal domains that can be applied across DNSFilter deployments to reduce manual overhead and improve reliability when traveling.
Tivly has experienced issues where DNS resolution fails in environments such as airports or airplanes, primarily due to the need to manually maintain a local domains list for captive portals. These disruptions are particularly problematic for users who travel frequently and rely on seamless connectivity in transit.
Requested Feature:
A built-in, dynamic list of known captive portal domains, particularly for airlines, airports, and public Wi-Fi providers DNSFilter should maintain and update this list centrally (similar to threat feeds or content categories).
- Option for customers to opt-in to apply this list globally or per-policy
- Ideally complements or integrates with the existing Local Domains functionality
Customer Value:
- Reduces administrative burden and reliance on guesswork for domain inclusion
- Prevents common DNS resolution failures for traveling users
- Improves user experience and confidence in DNSFilter coverage during travel
Minetta Gould
marked this post as
launched
🎉 Launched (via a different approach): We’ve addressed this need with Travel Wi-Fi Mode, which helps end users access captive portals with a click of a button when they’re on networks like airlines, airports, and public Wi-Fi.
Rather than maintaining a centralized list of captive portal domains, Travel Wi-Fi Mode gives users an on-demand way to connect successfully while keeping DNS protection in place. It’s optional and can be enabled either manually or via an MDM script.
Closing this request out as complete based on that functionality—and thanks for the thoughtful breakdown of the use case!