My understanding is that the Meraki device is listening for that DNS request. If you have a DNS server running like AD DNS on your network, you could create a forward lookup zone for my.meraki.com, or mx.meraki.com etc. and point to the clients to that DNS server which will fail to load anything. Thinking outside of the box, but have done this in the past as a quick way (without web filtering) to block entire domains. This obviously only works if you restrict the clients DNS to your DNS server. Otherwise they can just change it to something else and would work globally. ... View more

I upgraded my MX95 to 18.205 (or 6) at the time and it caused my CPU usage to go up to 100%. Since there isn't a way to check the CPU, I only caught it because of the summary report showing 100% utilization. I'm sure it would have eventually crashed. I'm still hesitant to move up to 18.207 because of that. I ended up rolling back to 18.107.7 and it was fine again. ... View more

I noticed this yesterday as well. The lookups were failing, but everything else was working for me. Internal webpages were also working over the vpn.   I thought with 18.x code it moved to Talos instead of Brighcloud? (or ealier. I cant remember)   ... View more

Same here. its going in and out for me. APs and MX showing offline ... View more