We have the similar issue. However, we are able to ping and traceroute the DNS server. IP were statically configured, including the HQ DNS server, on the PC behind the MX remote branch. We tried as well to nslookup their internal IP and it is working plus able to access internal applications, but PC cannot communicate to the internet. Using a public DNS, we are still able connect to internet but cannot access their internal applications, though DNS server is reachable using ping and traceroute. ... View more

Wow.. that's crazy! I am less than impressed with that decision from Cisco.   I have 5 site to site vpn's setup and my full network is exposed to them when I want to restrict their access to a couple of internal ip addresses...??   Come on Cisco , you should know better!     ... View more

Thanks for responding.  I guess my next question is I have a MS-220 and a couple of MR55.  Do I really need buy the Meraki firewall or does the switch provide me with some internal security at all?   Or can I use my AX11000 ROUTER as the firewall?  Your thoughts would be appreciated. ... View more

We swapped out our MX84's for MX100's and it happened with 2 MX100's in an HA configuration.  Meraki does not recommend a direct connection for heartbeats between the 2 MX devices any longer.  We now have 2 MX100 devices with the HA one powered off.  This is ridiculous. ... View more

Can I create a template for switches and not have to include MX devices?  I have 2 networks bound to a template and I recently was asked to create a vlan specific to one of those networks on the MX84 which is where all of our VLANs are defined.  If I create the VLAN for the one network, it'll be created on the other and we don't want that.  I've been asked to change a few settings on the MX84 so I wanted to keep those individually configured and just have a profile for the switches and APs since that one-off VLAN would not be configured on or used by the switches. ... View more

I agree with Adam.  I would not expect that to work.  Printers and shares on a different VLAN need to be addressed directly by IP. ... View more

the cobber interfaces is Marvell Alaska V 88E1680 chips and the fiber is Marvell 98DX3233A1. Maybe marvell has some spec. pdf.   The SoC in a Microsemi SmartFusion2 - https://www.microsemi.com/product-directory/soc-fpgas/1692-smartfusion2   Memory is SK hynix - https://www.skhynix.com/products.view.do?vseq=913&cseq=74 and Nand flash from Spansion.   It´s all the same hardware in the 120 series and nothing home grown. All bougt from other venders. https://www.rovi.dk/meraki-ms120-8-switch/     ... View more

@RH6379 wrote: We're installing 12 MS-120 switches in a remote office and the switches are showing a DNS misconfigured error when we use the IP of the mgmt vlan as the DNS Server.  That is configured on an MX84.  Is your MX84 not configured as a DNS proxy perhaps? If it's not relaying and returning DNS queries and responses for clients, then the switch isn't going to connect either. ... View more

Correct, obviously doesn't need to be those ports.  Could just as easily be 47/48 or whatever.   ... View more