Apple Screen Time Conflicts with DNS Content Filtering

Apple's Screen Time feature can interfere with DNS-based content filtering. Learn how to identify the conflict and configure your devices so CleanBrowsing works reliably.

Step 1: Understanding the Problem

Apple's Screen Time feature, available on iOS 12+ and macOS Catalina+, includes a Content & Privacy Restrictions module with its own Web Content filtering. When this feature is active, it intercepts DNS requests at the device level — similar to how CleanBrowsing and other DNS-based content filtering services work.

Since Screen Time operates at the device level, it takes precedence over network-level DNS filtering, creating two competing filter systems that interfere with each other.

Step 2: How the Conflict Occurs

Both Screen Time and CleanBrowsing attempt to control web traffic by intercepting DNS requests:

  • CleanBrowsing filters content at the DNS level by resolving blocked domains to a block page IP address
  • Screen Time intercepts requests locally on the device, applying its own allow/deny rules before the DNS query reaches the network

When both are active, Screen Time's device-level interception overrides the network configuration. This can cause DNS queries to bypass CleanBrowsing entirely, or create unpredictable behavior where some requests are filtered by Screen Time and others by CleanBrowsing.

Step 3: Symptoms of the Conflict

You may be experiencing a Screen Time conflict if you notice:

  • CleanBrowsing filters work on other devices but not on Apple devices
  • Blocked sites load intermittently or inconsistently on iOS/macOS
  • The CleanBrowsing block page does not appear when accessing blocked domains
  • Running nslookup -type=txt debug.cleanbrowsing.org on the device does not return CleanBrowsing filter information
  • DNS-over-HTTPS or DNS-over-TLS profiles are not working as expected

Step 4: The Fix — Disable Screen Time Web Content Filter

The solution is to disable Screen Time's Web Content filtering and rely solely on CleanBrowsing for content filtering. This eliminates the device-level interception and allows network-based DNS filtering to function as intended.

Why this is the right approach:

  • CleanBrowsing provides more comprehensive filtering with regularly updated block lists
  • Network-level filtering protects all apps, not just Safari
  • You avoid the unpredictable behavior caused by competing filter systems
  • You can still use Screen Time's other features (app limits, downtime, etc.) without conflict

Step 5: Recommended Configuration

For the best results, use this configuration:

FeatureSettingReason
Screen Time → Web ContentUnrestricted AccessPrevents DNS interception conflict
Screen Time → App LimitsUse as desiredNo conflict with DNS filtering
Screen Time → DowntimeUse as desiredNo conflict with DNS filtering
Network DNSCleanBrowsing IPsHandles all content filtering

You keep the benefits of Screen Time for app management and time limits while relying on CleanBrowsing for web content filtering.

Step 6: Disable Web Content Filter on iOS / iPadOS

  1. Open Settings on the iPhone or iPad
  2. Tap Screen Time
  3. Tap Content & Privacy Restrictions
  4. Enter your Screen Time passcode if prompted
  5. Tap Content Restrictions
  6. Tap Web Content
  7. Select Unrestricted Access (instead of "Limit Adult Websites" or "Allowed Websites Only")

After changing this setting, verify CleanBrowsing is working by visiting a domain that should be blocked, or run a DNS debug check.

Step 7: Disable Web Content Filter on macOS

  1. Open System Settings (or System Preferences on older macOS versions)
  2. Click Screen Time
  3. Click Content & Privacy
  4. Enter your Screen Time passcode if prompted
  5. Click Content Restrictions
  6. Under Web Content, set the Access to Unrestricted

Verify the fix by opening Terminal and running:

nslookup -type=txt debug.cleanbrowsing.org

The response should confirm you are using a CleanBrowsing filter.

Need more help?

Contact our support team for assistance.

Contact Support