MX Uplink DNS Behaviour

AY2022
Getting noticed

MX Uplink DNS Behaviour

Greetings All. 

 

Came online and noticed one of the remote network's WAN 1 was showing 'failed' status. 

Checked and discovered it was caused by a 'disruption' in the existing DNS (provided by ISP). 

Changed to Google DNS and line came back up. 

 

At the same time WAN 2 remained 'Active'. 

 

Would like to know whether there's a documented KBA on such finding. 

Will a failed DNS configured lead to a 'failed' status of the WAN? 

 

2 Replies 2
alemabrahao
Kind of a big deal
Kind of a big deal

There will certainly be a failure, devices communicate with the Meraki Cloud via Meraki addresses.
 
Just read the Meraki architecture documentation.
 
I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
KarstenI
Kind of a big deal
Kind of a big deal

This is documented under Connection Monitoring for WAN Failover.

If you found this post helpful, please give it Kudos. If my answer solves your problem, please click Accept as Solution so others can benefit from it.
Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels