Dns is misconfigured meraki switch. I still have more testing to do.

Dns is misconfigured meraki switch 67. Access point is now randomly showing a solid blue light on and Configure static DNS on the MX to point to either the same settings that are on the EE router or a public DNS such as 1. Access point is now randomly showing a solid blue light on and DNS is outside because at the time we deployed them we didn't have an available internal DNS server. My suggestions are based on If you're seeing a number of STP changes then something is occurring in the network that is causing STP to reconverge. Meraki Community. Use upstream which broadcasts the gateway ip as the dns server and then sends the traffic upstreme to the ISP,s dns is where the issue lies. Accepted Solution ‎Jun 7 2023 8:00 PM. The same issue occurs where there are no DNS responses. This is when the network crashes hard and we lose the network across our whole No headers Cisco Meraki APs alert "DNS misconfiguration" when a Linksys WRT54GS broadband router supplies unresponsive DNS servers via DHCP. After doing a clean reboot and confirming DNS services started OK on those servers, I rebooted By the time I got two switches to talk, I noticed that I had "DNS is misconfigured" alerts on both the switches and the AP's. The primary and secondary DNS servers for all of these are set to our two internal domain controllers with DNS server running. A packet capture shows that DNS DNS on the WAN1 uplink and use Google DNS on the WAN 2 Uplink. Nothing has changed. AP can not connect outside DNS server directly and we configure ip address of internal DNS server in our AP and we configured internal DNS server provide lookup for meraki. When Meraki Go hardware is unable to resolve DNS queries, this article helps shed light on what to do. cancel. That tells me there's an internet connection issue. Try setting DNS to a public IP such as 1. Do you know of a way to change this? DNS Misconfigured on MX100 DNS on the WAN1 uplink and use Google DNS on the WAN 2 Uplink. SoCalRacer. I finally noticed the issue as I was in the DNS is misconfigured. I did that, but that didn't work. Our AP is now connecting the internet via Proxy and Proxy sends DNS query to outside DNS server and it handle the name resolution curretly. WAPs/switches) you can assign external DNS as secondary as this can help with monitoring/troubleshooting. I notice that my stack switches some of the member switch got this alert message indicate DNS is misconfigure. 2 we received a 'misconfgured DNS' alert on the dashboard. I tried to change one of the DNS settings to 8. We have also tried switching to Cloudflare and Google DNS. Turn on suggestions. This is due to the fact that if your internal DNS servers go down, then the device will become problematic or go down completely. Perhaps the EE router has had an update that is stopping the MX get DNS settings from it. Access point is now randomly showing a solid blue light on and >You're thinking that if the VPN destination is set to 0. We started about a month ago and have our main areas mainly done already - Close to 60 switches, with about 40 already deployed. But in support of a Client, I have recently installed an MS225-48FP. They are both using exactly the same DNS and on the same subnet which is our switch mgmt subnet so there are no firewall rules blocking Overview . Thanks for the assistance. There's an option for passthrough IP on the Inseego. Upon checking the MX80 appliance status, it was red, with "DNS is misconfigured". They are both using exactly the same DNS and on the same subnet which is our switch mgmt subnet so there are no firewall rules blocking This is caused by your MR and MS appliances being unable to resolve domain names over the configured DNS servers. The switches are losing connection to the meraki cloud, which tells me they are losing connection to the internet in general. MX is static of course, the Switch and AP's were static, but since we rolled back, we left them as DHCP for the next attempt. If I am configuring DNS on the Meraki MX on the network edge under uplink settings, then configuring DNS on each individual switch in my network as well, if I don't use the same settings. In addition to the MX250 going off line randomly, I get a DNS misconfigured message that cycles through the 5 switches attached. Kaleb Mohr, CCNA. Using DNS servers located at a data center on existing and new VLANs. Though I would through this here and see if anybody has any suggestions. What will be the remedy? 208. All AP is configured with IP Static with dns primary 1. The PPPoE service also appears to use the ISP DNS, which seems to override the VLAN DNS settings. I have a switch thats showing me the exact same alert even though its DNS is configured the On the Meraki dashboard it is reporting DNS is misconfigured. Notice: Split DNS mode is only available when select "Only send We are in process of migrating over to a complete Meraki Switch site. If using internal DNS maybe have a public DNS server like 8. Even Cisco Switches in their logs show "Duplicate IP". which would a client attached to one of those switches use, the MX or the MS? Shown DNS Misconfigured, but worked after a few minutes. My customer is experiencing an issue where the switch stack will alert "DNS is misconfigured, switch disabled" intermittently. 3. 1 and dns secondary 8. Use Google Public DNS Google maintains publicly available DNS servers. 220 / not mandatory but i believe its preferred when specially you using Cisco Meraki AMP - then use the same DNS address down in Meraki Community cancel. 220 / not mandatory but i believe its preferred when specially you using Cisco Meraki AMP - then use the same DNS address down in the stack with every Ability under "General" For security appliances to have an alert setup for "DNS Misconfigured" as this helps to notify of any possibly latency or reason to changes to VPN traffic (especially when using the Auto-VPN feature in Hub/Spoke model). I have to admit I am not a fan of Meraki or any cloud based switch for that matter. From my testing it is related to the option "use upstream DNS", ISP DNS = pages load instantly. com, google. after changing the DNS in "DHCP"-Settings its fine again. The Cisco Meraki MX Security Appliance uses Dynamic DNS (DDNS) to update its DNS host record automatically each time its public IP address changes. I setup the DNS to 8. Any public DNS will work but we subscribe to Umbrella. I have a switch thats showing me the exact same alert even though its DNS is configured the Is this your only DNS or do you have other which can be set? Have this problems some times as well. On the Meraki dashboard it is reporting DNS is This is caused by your MR and MS appliances being unable to resolve domain names over the configured DNS servers. I still have more testing to do. 4. Apologies for the late reply, but no there By the time I got two switches to talk, I noticed that I had "DNS is misconfigured" alerts on both the switches and the AP's. The path to my switch is Internet -> pfSense -> Meraki. That does not affect your client devices at all, when the switch is alerting DNS is misconfigured, the clients are affected and cannot resolve DNS. If you have configured native VLAN for port on MX or switch port where switch or AP is connected and using VLAN tagging on IP configuration then you might encounter errors on the switch or AP. I have a switch thats showing me the exact same alert even though its DNS is configured the Meraki Community cancel. While all my other access points are working fine. | Network Engineer DNS settings affect the Meraki box you're configuring, e. Check these parameters to find the source of the issue: My customer is experiencing an issue where the switch stack will alert "DNS is misconfigured, switch disabled" intermittently. The duplicated IP switches remained "online" in the dashboard, and showed "disabled Switch Bad DNS". If a device reports issues with its DNS configuration, typically the device is not receiving responses to DNS requests. Are you using a non-Meraki VPN to Amazon AWS? Does the VPN destination include the DNS servers you are trying to reach (such as using a VPN to DNS Misconfigured on MX100 DNS on the WAN1 uplink and use Google DNS on the WAN 2 Uplink. 8 to see if there is a problem with Open DNS, but no luck. We have been experiencing an issue where an 8-Port POE switch keeps rebooting about once every half hour/hour. All AP can navigated on internet without problem. Using google DNS at this point. I'm wondering if it's just an issue with the switch or something, because I have tried completely disabling the rules I put in place and the switch always reports DNS misconfigurat Presently DNS policies are being configured on the Cisco Umbrella dashboard. 0 Kudos 208. Turn on suggestions I got alert from the dashboard saying "DNS is misconfigured" and on WAN 1 it has "Failed" status yet I have internet connectivity and my server is reachable outside my network and over the internet. google or any other dns = pages load instantly. 220. I too have DNS issues with meraki. 4 as the DNS servers. 220 / not mandatory but i believe its preferred when specially you using Cisco Meraki AMP - then use the same DNS address down in the stack Hi I just installed a MS210 3 switch stack and 2 MX84s in H/A configuration using 2 ISPs and a VIP for each of those. My suggestions are based on Our AP is now connecting the internet via Proxy and Proxy sends DNS query to outside DNS server and it handle the name resolution curretly. Meraki devices rely on DNS to resolve dashboard URLs. Clients on the network cannot resolve DNS requests but can get to the internet. You will need to navigate to Umbrella dashboard from Cisco Secure Connect. Switch and APs are sometime showing DNS mismatch and disconnecting from Network. Apple remote desktop software is having issues with many deivces now reporting authentication issues. DNS misconfigured on switch. Additionally, users What I found was that 1 of our switches and all of our Meraki MR33/MR34 AP's were showing DNS misconfiguration errors. | Network Engineer I found that when I plugged it into the main switch, the switch port I plugged it into was set for another vlan thereby causing the issue, because when I plugged the switch directly into the firewall all issues seem to resolve. What I found was that 1 of our switches and all of our Meraki MR33/MR34 AP's were showing DNS misconfiguration errors. After the switch is We have been experiencing an issue where an 8-Port POE switch keeps rebooting about once every half hour/hour. The following article describes the process of resolving the "DNS Misconfiguration" alert that can appear when using a Linksys WRT54GS in combination with Cisco Meraki access points. The default option is to use the Upstream DNS, which is provided by your internet service provider. 8. 1, or whatever your provider's DNS is)? Are there other Meraki devices on the network? And if yes, do any of them have the same problems? Actually had it happen with a MX67 yesterday. 4 so you have clean DNS in case the tunnel or your server internally does not work. That didn't work. I spoke to Meraki support at one point and he stated that the updates on the MR32s needed to be rolled back to be better compatible with the current version of the other APs on the network, but the issue still persists. 8 and 8. Accepted Solution With ‘Split’ DNS Secure Client only allows internal DNS queries via the VPN interface, and only allows external DNS queries via the LAN/physical interface. 16. Alternatively, Google DNS and Open DNS are built-in selections. The Cisco's all also have their management in vlan 2 and they can ping out to the internet fine. 8 on one computer and now it can access to internet. 1. If the DNS server is connected to a Meraki switch can you see the connection history of the port and are there any errors shown? Actually had it happen with a MX67 yesterday. After all the switches are boot up after the power failure in the server. Meraki support took a PCAP this morning working with the customer and could see DNS Unfortunately, I have yes. Thanks for the suggestions and the link to the best practice We are going through our network and checking ports etc Will keep you posted on the - The Meraki device is sending DNS request but there is no DNS replies. - The Meraki device is sending DNS request but there is no DNS replies. Meraki support took a PCAP this morning working with the customer and could see DNS They just need a valid DNS IP. We have also tried switching to We are in process of migrating over to a complete Meraki Switch site. Solution i force reboot the switch having this issues by unplug the power cable and plug back. My suggestions are based on Switch and APs are sometime showing DNS mismatch and disconnecting from Network. By the time I got two switches to talk, I noticed that I had "DNS is misconfigured" alerts on both the switches and the AP's. If the DNS server is connected to a Meraki switch can you see the connection history This is caused by your MR and MS appliances being unable to resolve domain names over the configured DNS servers. which would a client attached to one of those switches use, the MX or the MS? In my Case, my customer moved their switches from DHCP to Static, When they did that, some of their switches ended up with Duplicate IPs. g. Then it got stranger. I configured the DNS settings on both the MX uplinks the same on the warm and spare, but the DNS setting differ on the switches. If this is happening again and again, then this will cause the switches to be unable to contact their DNS servers (either due to high-CPU, or pure network traffic), so the DNS misco Check where is your mismatch, like : if you add the MX84 the Cisco OpenDNS address - 208. All switches and access points are alerting with Bad DNS. Turn on suggestions DNS Misconfigured on MX100 DNS on the WAN1 uplink and use Google DNS on the WAN 2 Uplink. we start to see switches alert and say DNS is misconfigured. I have used the "Google machine" and also Meraki's knowledgebase with little to no assistance. We do use Spectrum (our ISP) DNS on the WAN1 uplink and use Google DNS on the WAN 2 Uplink. Access point is now randomly showing a solid blue light on and A client was experiencing intermittent issues on their network. I had network, but no Internet. 222. Meraki support took a PCAP this morning working with the customer and could see DNS - The Meraki device is sending DNS request but there is no DNS replies. Testing umbrella connectivity from the dashboard also shows an inability to connect to umbrella DNS servers. We have 2 MX100's (Primary and secondary) and both have been showing the DNS misconfigured alert for about a week. Tried multiple restart, changed the rstp root setting to this switch (it changed by itself many times). Best practice is to just use an external IP since it is really only for the switches to. 0. It's more likely that something is failing resolution using that DNS server. I just need to find out what If the switch is rebooting and there isn't anything obvious in the event log, I'd suggest contacting Support. added to what has said, id draw out the connectivity you have on a piece of paper (might need a big piece) to make sure you haven't inadvertently connected switches round in a loop. 1 it should then hand that out to clients via dhcp. I read on a help page to add a UDP port 53 rule to the firewall. 107. 7 Replies 31717 Views Meraki MS switches interoperability by Boomer on ‎Aug 7 2017 11:39 PM Latest post . Additionally, the Umbrella network devices API can be linked on a template parent network so that children networks bound to the template can easily leverage My customer is experiencing an issue where the switch stack will alert "DNS is misconfigured, switch disabled" intermittently. 0 208. Over the past few days, I have noticed DNS issues on devices connected to the Meraki switch even though pfSense appears to be fine. To get to the Umbrella DNS Policies page from the Secure Connect Dashboard click on the DNS link in the Policy Count card or go to the menu and click on DNS under Policies column. 8 as a secondary if your network manager allows the use of external DNS on internal equipment / clients. Regards Regarding DNS: Yes it needs DNS. for being able to talk to the dashboard. com. What will be the remedy? Shown DNS Misconfigured, but worked after a few minutes. But the I tried that, and it did fix the DNS errors on all of the AP's, but the switch is still showing DNS as misconfigured. I have the dreaded DNS misconfiguration errors on one of my switches, it started after I split two aggregated ports on two switches connected in a stack. Hello, we have about 900 AP´s in our organisation configured with static IP´s. Thanks. I checked with my ISP and they tell me nothing is wrong on their end, and that it's my bandwidth utilization (over 90%), but to have connection interruptions on a weekend when no one is on We have been experiencing an issue where an 8-Port POE switch keeps rebooting about once every half hour/hour. DHCP is at the MX, DHCP scopes are defined for the old and new VLANs. I have a switch thats showing me the exact same alert even though its DNS is configured the We have a site-to-site VPN set up between our Office network and AWS. I have a switch thats showing me the exact same alert even though its DNS is configured the Question regarding DNS configuration on the Meraki MS switches. Meraki told me to change the DNS to public 8. Have you tried with a different DNS (like umbrella)? I am not a Cisco Meraki employee. We'll see how that works. I also rebooted a switch and that didn't help either. Meraki support took a PCAP this morning working with the customer and could see DNS Use the Edit menu in the upper right and choose the "Change DNS server" option from the pop up. which would a client attached to one of those switches use, the MX or the MS? Apologies for the late reply, but no there is no correlation as far as I can tell. The next screen contains several options for configuring the DNS service for your network. 4, 1. This is when the network crashes hard and we lose the network across our whole DNS Misconfigured on MX100 DNS on the WAN1 uplink and use Google DNS on the WAN 2 Uplink. Therefore, you will see the "DNS misconfigured" The behavior you are having is not just related on getting an IP address, you should ensure all the traffic coming from the device, the upstream device is able to forward the reply. 222 and 208. I'm wondering if it's just an issue with the switch or something, because I have tried completely disabling the rules I put in place and the switch always reports DNS misconfiguration. There is no MX switch in the network, we have the vlans and their SVIs configured on the MS425 Core switches. 0 Kudos Subscribe. The Comcast modem will be configured with the default ISP DNS servers, but the Meraki is set to push out Google DNS. Hello, I am looking for some insight into configuring DNS on Meraki Switching VS Meraki MX. The Meraki serves as the customer. 220 / not mandatory but i believe its preferred when DNS settings affect the Meraki box you're configuring, e. This is when the network crashes hard and we lose the network across our whole We are in process of migrating over to a complete Meraki Switch site. The switches, even on days with no one on the network, will alert me that they are having trouble communicating with the meraki cloud. I spent hours trying to diagnose this on the gear. Huh. Everything was getting resolved by internal DNS, but couldn't get out. The DNS bad or misconfigured alert can sometimes be a bit of a red herring. I tried that, and it did fix the DNS errors on all of the AP's, but the switch is still showing DNS as misconfigured. I have a switch thats showing me the exact same alert even though its DNS is configured the DNS Misconfigured on MX100 DNS on the WAN1 uplink and use Google DNS on the WAN 2 Uplink. Thank you for the thought. 220 / not mandatory but i believe its preferred when specially you using Cisco Meraki AMP - then use the same DNS address down in the stack with Actually had it happen with a MX67 yesterday. Can you support why i am getting the same. As with almost every device used on the internet, Meraki devices rely on DNS to resolve the dashboard URLs. But it is not recommended to mix internal & external The Switch and AP are pointing to the Meraki router, but are both reporting "DNS is Misconfigured" error. 4. 220 / not mandatory but i believe its preferred when specially you using Cisco Meraki AMP - then use the same DNS address down in the stack Shown DNS Misconfigured, but worked after a few minutes. 208. That does not affect your client devices at all, these would receive their DNS settings via DHCP (possibly). The primary and secondary DNS servers for all of these are set For network equipment (e. I think Meraki has a fallback in case DNS can‘t be resolved, they try very hard to get to the dashboard 🙂 I recommend configuring DNS server on the switches (and other Meraki gear) you can always reach, like 8. I have lots that point to the private IP of my MX (that's also the DHCP server) and they work just fine. We are in process of migrating over to a complete Meraki Switch site. I thought that if I disconnected the new switches the problem would go away since it was their installation that caused it. If the switch is rebooting and there isn't anything obvious in the event log, I'd that's quite reasonable but mine is a little bit different. Updating DNS, trying alternate DNS, checking IP NOTE: Umbrella integration is linked on a per-network basis to the Meraki dashboard, so the Umbrella API key and secret must be entered on every Meraki network that requires Umbrella integration. The network is straight forward ISP Modem > Router > PoE Injecto The AP constantly reports misconfigured DNS even though its the same DNS that the Meraki switches use, I have also check for upstream firewall rules and thats not the issue. DNS misconfigured on switch by Mike_Rapp on ‎Aug 10 2017 12:00 PM Latest post on ‎Aug 14 2017 3:41 PM by BHC_RESORTS. I tried using Google public My customer is experiencing an issue where the switch stack will alert "DNS is misconfigured, switch disabled" intermittently. I have a switch thats showing me the exact same alert even though its DNS is configured the same as every other switch on the network. After setting up the switch with manually configured DNS, I not that the switch is still attempting to resolve names through Google (8. There is not bad DNS or DNS misconfigured messages on random switches despite them all using googles name service (8. common switch or network path? 0 Kudos I have the dreaded DNS misconfiguration errors on one of my switches, it started after I split two aggregated ports on two switches connected in a stack. Configuration. If the switch is rebooting and there isn't anything obvious in the event log, I'd Meraki Community cancel. Configure static DNS on the MX to point to either the same settings that are on the EE router or a public DNS such as 1. Shown DNS Misconfigured, but worked after a few minutes. Have turned the WiFi back on the EE router for testing & devices I have discovered that our firewalls, switches & APs were all misconfigured & have now got the firewalls & switches into a state where DNS is now working. The issue started 5 hours ago and is happening at different sites with separate internet connections. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Though I would through this here Meraki AP DNS Issues So a bit of context; I am new at the company, two weeks in & every day I am finding issues with the network that the MSP has been managing for over 2 years. This is for only one AP, rest AP's is showing online. Meraki Community cancel. I pointed them to my internal DNS servers and they went green for a minute but then went back to orange saying DNS misconfigured. I have discovered that our firewalls, switches & APs were all misconfigured & have now got the firewalls & switches into a state where DNS is now working. Meraki told me to change the DNS to public 8. They have access to a much more robust event log that will likely indicate why the switch is really rebooting. DNS Misconfigured on MX100 DNS on the WAN1 uplink and use Google DNS on the WAN 2 Uplink. How can i My only point of confusion lies in the behavior this causes, when the switch is alerting DNS is misconfigured, the. Now the central DNS IP will change, ist there a way to change it for The AP constantly reports misconfigured DNS even though its the same DNS that the Meraki switches use, I have also check for upstream firewall rules and thats not the issue. I configured the DNS settings on both the MX uplinks t These are the only Meraki switches on the network currently, everything else is Cisco. All Meraki gear - MX84, MS225-48LP, and MR33's. x). Both are down. Use Cisco Umbrella Cisco Umbrella uses the Internet's infrastructure to enforce security and block malicious activity before a connection is @ludwigbery This is most likely a false positive, if the device is showing active in the dashboard and you can adjust the config on the device and it sitck then I wouldn't worry. They are both using exactly the same DNS and on the same subnet which is our switch mgmt subnet so there are no firewall rules blocking Hi, i Have a infrastructure with 7 AP Meraki ( six MR74 and one MR33) , but for a month ,i have a problem with yellow alert "DNS is misconfigured". I think ill be getting local access to them later and taking a look to get the info straight from the horses mouth. Meraki support took a PCAP this morning working with the customer and could see DNS Hi All, I am getting an alert in AP "DNS is misconfigured". On the Meraki dashboard it is reporting DNS is misconfigured. Reply. Accepted Solution. 8). This is when the network crashes hard and we lose the network across our whole They don't need a public DNS server. which would a client attached to one of those switches use, the MX or the MS? If using internal DNS maybe have a public DNS server like 8. This feature is useful because it allows the administrator to configure applications such as client VPN to access the MX by its hostname which is static instead of an IP address that may change over time. 220 / not mandatory but i believe its preferred when Try setting a public DNS IP manually. Even after a reboot. The AP constantly reports misconfigured DNS even though its the same DNS that the Meraki switches use, I have also check for upstream firewall rules and thats not the issue. There are various different switches on different sites that have this issue. com and yahoo. I have a switch thats showing me the exact same alert even though its DNS is configured the Hello, I am looking for some insight into configuring DNS on Meraki Switching VS Meraki MX. . The APs on the other hand seem @ludwigbery This is most likely a false positive, if the device is showing active in the dashboard and you can adjust the config on the device and it sitck then I wouldn't worry. Whether internal or external. Access point is now randomly showing a solid blue light on and That indicates the AP itself is having issues reaching the DNS server. Have you tried other DNS IPs (8. x. One switch is fine the other has a DNS issue now. this is my last day report Switch and APs are sometime showing DNS mismatch and disconnecting from Network. 4 to resolve DNS. 2nd one says DNS Misconfigured. I believe the DNS issue to be a symptom of another underlying problem. This is caused by your MR and MS appliances being unable to resolve domain names over the configured DNS servers. Accepted Solution The Meraki serves as the Meraki Community cancel. We have a management VLAN for our switches and the MS350 is the L3 and hosts DHCP with 8. Navigate to Wireless > Configure > Access control in Dashboard; Choose the desired SSID from the drop-down menu at the top of the page; Under Client IP and VLAN, select Meraki AP assigned (NAT mode); For Custom DNS servers, enter the preferred custom DNS IP addresses. The meraki switch says that the DNS is missconfigured, we don't know how to troubleshoot it because its all good with our DNS on the other meraki location. 1 or 8. This alert is presented when DNS lookups fail to the following hosts: DNS is, usually, set automatically with DHCP (when Hello, during a Meraki MX95 firmware upgrade from version 16. One of the most common DNS configurations when assigning a static IP address to a Meraki device is to use one ISP-provided DNS server and one well-known public DNS service such as Google (8. Got it hooked directly to a DIA Ethernet circuit. My suggestions are based on I have the workstations set to use OpenDNS, and all the VLANs, apart from one which which uses the DNS addresses provided by the ISP that also delivers the TV service (that is what the service expects). The only common denominator for the alert is that they only come from our MR32 AP's. The MXs appear fine. Maybe we should switch both to Spectrum. If I am configuring DNS on the Meraki MX on the network edge under @ludwigbery This is most likely a false positive, if the device is showing active in the dashboard and you can adjust the config on the device and it sitck then I wouldn't worry. which would a client attached to one of those switches use, the MX or the MS? Got it hooked directly to a DIA Ethernet circuit. I have the DNS of my Meraki switch set to the pfSense box, but the pfSense box isn't guaranteed to be on/working. Kind of a big deal ‎Aug 12 2020 12 We have been experiencing an issue where an 8-Port POE switch keeps rebooting about once every half hour/hour. A maximum of 2 DNS servers can be specified; Click Save to apply Hi two of my MR33 access points are behaving strangely 1st one goes from Online to Alerting every few hours and says IP Address conflict on up-link. I ha Meraki Community cancel. 0/0 that the DNS queries are going through the VPN? I'm not sure, but I'm thinking that is what it could be. This article describes best practices for configuring DNS servers on the WAN interfaces of all Cisco Meraki products. Almost every time there is a VPN connectivity change it is usually due to the security appliance having a DNS misconfigured or detecting a Unfortunately, I have yes. Had this happen in my data center when a switch failed and everything lost connection to the DNS behind said failed switch. Only switches and APs exists on that VLAN All switches and access points are alerting with Bad DNS. 8 to version 18. Clients will use 8. qomflch wysho xmluavy tewjalh yrjeqm ivwvit dzjzq ghio uvl vjkgeu