• 

  Brian Zick

  • February 27, 2025 13:39

  Please add the captive portal for Delta, DeltaWiFi.com, to this list. 

   

  Source: https://www.delta.com/us/en/onboard/inflight-entertainment/onboard-wifi (Step 3)

  1
• 

  Minetta Gould Community Team DNSFilter Staff

  • February 28, 2025 18:23

  Thanks for the suggestion, Brian Zick —added to the list!

  1
• 

  Brian Zick

  • February 28, 2025 18:26

  Thank you!

  1
• 

  Amanda Hunt

  • April 17, 2025 18:10

  Please add captive.apple.com for Apple devices. 

  1
• 

  Minetta Gould Community Team DNSFilter Staff

  • April 17, 2025 21:07

  Thanks for the suggestion, Amanda Hunt —added to the list!

  0
• 

  Karik Hill

  • June 05, 2025 19:41

  How about removing the hyperlink from the local domains so we don't accidentally click through while trying to copy.  

  0
• 

  Minetta Gould Community Team DNSFilter Staff

  • June 06, 2025 14:58

  Great suggestion, Karik Hill ! Thanks for helping make our documentation better 💖

  1
• 

  Kyle Murphy

  • June 27, 2025 13:26

  Thank you for this list!
  We have a client end-user who is traveling and discovered they can't connect to the Hilton URL “secure.guestinternet.com”. Will adding the URL to the Allow List of their assigned filter policy function the same way as adding it to the Local Domains? And will they need to connect to a different internet to pull down the new setting changes before it will start working? 

  1
• 

  Minetta Gould Community Team DNSFilter Staff

  • June 27, 2025 17:07

  Hi Kyle Murphy thanks for reaching out! 

  Adding "secure.guestinternet.com" to the Allow List is not the same as adding it to Local Domains. The Allow List lets DNS traffic to that domain through DNSFilter, but Local Domains ensures DNS queries for that domain are handled by the local network’s DNS (often needed for captive portals like Hilton’s).

  We recommend following this article's suggestions in order. Start by having the user: 

  • Open a browser and try accessing any domain
  • Turn off and back on the device's Wi-Fi
  • Restart the device
  • Open the mac agent's icon (small globe in the task bar) and click Access Captive Network

  If none of these local steps work, add "secure.guestinternet.com" as a Local Domain in the DNSFilter dashboard. This allows the device to bypass DNSFilter to reach the captive portal login properly. 

  If the user is already unable to connect, they may need to join another network temporarily to sync the updated Local Domains setting with their Roaming Client. After syncing, they can reconnect to the Hilton Wi-Fi.

  Let us know if the issue persists and we can look into some different troubleshooting steps!

  1
• 

  Daniel Stranathan

  • February 24, 2026 18:58
  • Edited

  Now that 2.3.12 for Mac will be available soon, and it will offer “MDM support of Travel Wi-Fi Mode” (announced Jan 21 here), Can you point me to your docs on how to configure Travel Wi-Fi Mode in MDMs such as Jamf Pro?
  
  Will Travel Wi-fi Mode be managed via a MDM profile scoped to domain com.dnsfilter.agent.macos or perhaps written to a flat text config file (/Library/Application Support/DNSFilter Agent/daemon.conf) or will it be managed elsewhere?

  1
• 

  Minetta Gould Community Team DNSFilter Staff

  • February 25, 2026 00:08

  Hey Daniel Stranathan, happy to help out. 

  Travel Wi-Fi Mode is not managed via a separate MDM profile and doesn’t require manual edits to daemon.conf.

  It’s configured through the deployment script. You simply add allowExtensionBypass=true to the temporary config section of the installer script, as outlined in the Travel Wi-Fi Mode article's silent install section. The setting is written during installation and applied by the agent.

  So from an MDM perspective, this is handled as part of your scripted deployment—not via a managed profile payload.

  1
• 

  Daniel Stranathan

  • February 25, 2026 14:18

  Install script is fine for new deployments, but we have 400 Macs with DNSFilter 2.2.0 and 2.3.8 installed already. Why run a monolithic script when the allowExtensionBypass key could be managed in a modern, dynamic MDM profile? 
  
  What is the recommended method for existing Macs that will (eventually) get auto-updated to 2.3.12?

  1
• 

  Minetta Gould Community Team DNSFilter Staff

  • February 25, 2026 19:46

  Daniel Stranathan  If the agent is already installed, you can push a script via MDM to update the config file in place. Our Engineering team tested the following and confirmed it works in their test environment:

  #!/bin/bash
  
  CONFIG_FILE="/Library/Application Support/DNSFilter Agent/daemon.conf"
  LINE_TO_ADD='allowExtensionBypass=true'
  
  # Check if the line already exists
  if grep -qF "$LINE_TO_ADD" "$CONFIG_FILE"; then
      echo "Line already exists in config. No changes made."
      exit 0
  fi
  
  # Add the line to the top of the file
  TEMP_FILE=$(mktemp)
  echo "$LINE_TO_ADD" | cat - "$CONFIG_FILE" > "$TEMP_FILE" && mv "$TEMP_FILE" "$CONFIG_FILE"
  
  echo "Successfully added '$LINE_TO_ADD' to the top of $CONFIG_FILE"

  If you’re running a Whitelabel deployment, the file path will differ slightly to match the Whitelabel agent name.

  After modifying the config, you’ll need to either:

  • Reboot the device, or
  • Restart the Roaming Client

  That said, since we don’t know all the other controls, profiles, or security tools in your environment, we strongly recommend testing this on a small subset of machines first and adjusting as needed before broad rollout.

  Let us know if this works for you or if anything else comes up!

  1
• 

  Daniel Stranathan

  • February 25, 2026 23:41
  • Edited

  Thanks - this works well for me. I had something similar in a testing group.
  
  1 I was under the idea that Wi-Fi Travel Mode would improve in 2.3.12 (i.e.; be a native setting that could be toggled in MDM, not require additional scripts etc. 
  
  2 Is there any difference in how Wi-Fi Travel Mode works in 2.3.8 compared to 2.3.12? My leadership was hoping that end-users wouldn't need to be trained on initialing this mode when traveling.

  1
• 

  Minetta Gould Community Team DNSFilter Staff

  • February 26, 2026 13:55

  Dashboard / native toggle support
  Dashboard-based controls for Travel Wi-Fi Mode are planned, but that work is not currently in progress. At this time, the setting still needs to be managed via a script update.

  We also don’t currently plan to make Travel Wi-Fi Mode automatically enabled by default, as we intentionally give customers control over how and when end users can initiate it.

  Behavior in 2.3.8 vs 2.3.12
  There are no functional changes to how Travel Wi-Fi Mode operates between 2.3.8 and 2.3.12, other than MDM controls where introduced in 2.3.9. The core behavior remains the same. 

  1
• 

  Brian Coyne

  • February 26, 2026 18:01

  Hi all,

  We are testing version 2.3.12 with Travel WiFi mode, but it doesn’t appear to be working as expected. It’s possible our testing scenario may not fully match the root issue.

  Here’s what we did:

  • We have a Mac running 2.3.12 with the allowExtensionBypass=true flag enabled.
  • When the Mac is connected to the internet, Travel WiFi mode is available as an option.
  • To simulate a captive portal scenario (such as at an airport), we enabled a captive portal on a home router.
  • We then forgot all saved WiFi networks on the Mac and rebooted it.

  Our goal was to replicate the real-world scenario where a user arrives at an airport with their Mac not connected to any WiFi network and attempts to join an airline or airport network that uses a captive portal.

  After rebooting:

  • The Mac was not connected to any WiFi network (as expected).
  • DNSFilter showed a “Fix Installation Issues” error.
  • The Travel WiFi mode option was no longer available.

  The only way to resolve this was to connect to a WiFi network which provides internet access (not a captive portal). Once connected:

  • The “Fix Installation Issues” error disappeared.
  • The Travel WiFi mode option returned.

  The issue we’re seeing is this:
  If the Mac is not connected to the internet when booted, Travel WiFi mode cannot be enabled because the agent displays "Fix Installation Issues". However, due to the captive portal issue, the user cannot connect to the internet. This creates a catch-22 situation.

  Please let us know if our testing approach is incorrect or if there’s a recommended way to handle this scenario.

  0
• 

  Daniel Stranathan

  • February 26, 2026 19:51

  I guess Im not following
  
  We went from 2.3.8 to 2.3.12 - there was no 2.3.9 as we discussed (it rolled into 2.3.12) I dont see any difference in Travel Wi-Fi Mode between 2.3.8 and 2.3.12… What exactly are “MDM controls” are new since 2.3.8? I have looked at the notes and dont see any changes.

  0
• 

  Minetta Gould Community Team DNSFilter Staff

  • February 26, 2026 21:38

  Brian Coyne I asked Casey to escalate your existing Support Request to the engineers for review. You'll be working with Tate now, so he should have you all set soon! 

  
  Daniel Stranathan  See our release notes for more detail, but v2.3.9 was the Beta release that enabled silent configuration (via MDM) of Travel Wi-Fi Mode as an option. Version 2.3.8 could only be configured on the device. 

  0

Please sign in to leave a comment.