Skip to main content

How can we help you?

Search

help Knowledge Base
forum Community
checklist Release Notes
event Events

Beta 2.4.2 (Mac)

Daniel Stranathan

Looks like 2.4.2 will be the biggest update for us in ~2 years since we purchased  DNSFilter. We are optimistic.

A few question for you regarding beta 2.4.2:

1 Following 2.4.2, does allowExtensionBypass=true still need to be manually added to our configuration (/Library/Application Support/DNSFilter Agent/daemon.conf)?

2 Can a DNSFilter binary (example /Applications/DNSFilter Agent.app/Contents/MacOS/DNSFilter Agent) be used to query for the exact version and build?

3 Rough ETA date on when 2.4.2 may move to production?

 

Comments

5 comments

Date Votes
  • Minetta Gould Community Team DNSFilter Staff

    Hey Daniel! Great questions—let me take them one at a time.

    1. The allowExtensionBypass config behavior is part of the documented MDM setup path since v2.3.9—that one hasn't changed with 2.4.2, so your existing configuration should carry forward as-is during upgrades.
    2. Could you clarify what you're trying to accomplish here? Knowing the end goal will help us point you in the right direction!
    3. 2.4.2 just hit the beta channel on June 15—if testing goes smoothly, production is currently targeting next week. A new changelog will post when the agent moves to Production.
    1
  • Daniel Stranathan
    • Edited

    1 That's not really a  ‘MDM solution’, thats just a script that can run via MDM (like any script). Im referring to moving DNSFilter settings like Wi-Fi Travel Mode to modern MDM/DDM porifles/configurations. These are dynamic, robust and can be automated,  better than running a script for a policy from a MDM server like Jamf Pro etc. 

    I was asking if TWM in DSNFilter 2.4.2 is still something admins need to set up or a feature that is already available to users without IT configurations. To my knowledge, DNSFilter is the only DNS security solution that requires extra steps to work in airports/airlines, etc.

    2 I was just curious if I can query DNSFilter directly from CLI, a script, over SSH etc to get the version (as opposed to having to use the macOS defaults commands to pull a version for a Info.plist buried in the app bundle).

    3 Good to know, thank you.

    1
  • Minetta Gould Community Team DNSFilter Staff

    Hey Daniel! Circling back on your questions:

    1. The allowExtensionBypass config still applies as a fallback for when automatic captive portal detection doesn't catch it—that's by design. Worth noting: as of 2.4.2, silent installs now also support CONFIG_ALLOW_MANUAL_CAPTIVE_PORTAL in the temporary config at /tmp/dns_agent.conf if that's useful for your deployment workflow. Here's an article about modifications that might be helpful. 
    2. You can query the version directly from the command line with:
    /usr/libexec/PlistBuddy -c 'Print CFBundleShortVersionString' /Applications/DNSFilter\ Agent.app/Contents/Info.plist

    Returns a clean version string that's easy to use in scripts too. 🙌

    1
  • Daniel Stranathan
    • Edited

    Minetta

    Version 2.4.2 for Mac has been out since June 23. But I still see version 2.13 as the default prod release in my tenant admin console. Im unable to toggle this.

    According to your release documentation, there is not a listing for what we should expect in terms of cadence for Mac 2.4.2. It's been 3 weeks and zero Macs have been updated to 2.4.2 (whereas Windows would be at or above 50% by week 3, according to docs).

    Thoughts?

    1
  • Minetta Gould Community Team DNSFilter Staff

    Sorry for the confusion here Daniel Stranathan : v2.4.2 was rolled back from the production release channel while we sort out a few things, which is why you're not seeing any macOS updates hitting your tenant and we missed updating the docs to reflect the pause.

    A new release is headed to the beta channel by end of this week, and the docs will update once that drops.

    0

Please sign in to leave a comment.

New post

Featured posts