May 27 2021
4:23 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
May 27 2021
4:23 AM
use content filter / meraki DNS although "specify nameservers"
it seems, that the MX disables its DNS functionality when selecting "specify nameservers..." in its DHCP configuration.
this effectively disables the content filter / MX DNS, right?
i'd like to use the MX content filter by specifying the MX as a forwarder in the configuration of the internal nameserver…
any idea?
Solved! Go to solution.
1 Accepted Solution
May 27 2021
7:45 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
May 27 2021
7:45 AM
Meraki mx does not run dns.
Content filter should still work regardless
2 Replies 2
May 27 2021
7:45 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
May 27 2021
7:45 AM
Meraki mx does not run dns.
Content filter should still work regardless
May 27 2021
8:02 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
May 27 2021
8:02 AM
very correct. also got a response from the meraki support: the MX inspects the url directly from the HTTP protocol, or the hostname/ip address from the HTTPS protocol.

Get notified when there are additional replies to this discussion.