Meraki dashboard connectivity lost after setting 1.1.1.3 DNS

SahadSalmiT
Getting noticed

Meraki dashboard connectivity lost after setting 1.1.1.3 DNS

Hi Guys, 

 

 I faced an issue when one of our engineers set the DNS as 1.1.1.3 in DHCP, the Meraki devices received that DNS lost connectivity with the dashboard, once the change reverted it regain the connectivity.

    I tried to "nslookup" dashboard.meraki.com, api.meraki.com and config.meraki.com with both 8.8.8.8 and 1.1.1.3, seems to be both DNS servers are resolving the DNS. What could go wrong here?

9 Replies 9
alemabrahao
Kind of a big deal
Kind of a big deal

Have you tried with OpenDNS?

 

I particularly prefer OpenDNS.

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.
SahadSalmiT
Getting noticed

Nope, the company requered to setup 1.1.1.3.

 

alemabrahao
Kind of a big deal
Kind of a big deal

As far as I know, Cloudflare IP is 1.1.1.1

 

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.
SahadSalmiT
Getting noticed

this one is bit aggressive and blocks malware and adult content. 

alemabrahao
Kind of a big deal
Kind of a big deal

This is a false sense of security, there are other tools that are much more effective at doing this.

Zscaler is an example. But that's okay, it's your choice.

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.
Brash
Kind of a big deal
Kind of a big deal

Seems odd on the face of it.

Do you have anything upstream blocking DNS lookups to 1.1.1.3?

SahadSalmiT
Getting noticed

Not at all, and on one site it didn't go offline for a few days and one day suddenly go offline. Reverting to google DNS fixed it immediately.

PhilipDAth
Kind of a big deal
Kind of a big deal

Is there an upstream firewall that might be blocking access to 1.1.1.3?

SahadSalmiT
Getting noticed

nope, no upstream firewall. All are directly connected to ISP. 

Get notified when there are additional replies to this discussion.