Home > Security Appliances > Other Topics > Cannot connect to wired.meraki.com

Cannot connect to wired.meraki.com

Table of contents
No headers
All DNS queries for wired.meraki.com that route through the MX are intercepted and responded to with an A record pointing to the local IP address of the MXs wired.meraki.com interface. If DNS queries for wired.meraki.com do not pass through the MX, DNS queries for wired.meraki.com will not resolve to the correct local IP address and clients will not be able to reach the local wired.meraki.com page. This issue frequently occurs when the DNS server used by clients on the LAN does not send its DNS queries through the MX as is the case when the DNS server uses a different default gateway. Below are the indicators of this problem and a solution.


Problem:

 - Content Filter Blocked websites are presented with the message "Hi there. You connected to wired.meraki.com, but you are likely not currently connected to a Meraki appliance" instead of "This website is blocked by your network operator." 

 - Local DNS servers are configured with a non-Meraki default gateway.

Solution: 

The Local DNS servers should be configured with an A Record for wired.meraki.com pointing to the LAN IP Address of the MX device.

ec2e9fdf-32a1-47d5-a887-dc0b4cedd04f

The steps below show how to create a wired.meraki.com DNS zone with an A record for wired.merak.com on a Windows DNS server.

1. Open the DNS Manager snap-in.

2. Right Click Forward Lookup Zones and choose New Zone... to open the New Zone Wizard.

9a479f2d-be57-43a6-b911-0c7ae4ef7332

3. For Zone Type choose Primary Zone and make sure Store zone in Active Directory is not selected. Click Next. 

530babae-cdcd-460b-b6ce-8ba4ed271ac5

4. Enter wired.meraki.com for the Zone Name and click Next.

69ae3a23-97e2-4032-bbb9-98b9e54ea059

5. For Zone File, leave the defaults and click Next.

6. For Dynamic Updates, make sure Do not allow dynamic updates is selected and click Next.

7. Click Finish.

8. Right click the wired.meraki.com zone in DNS Manager and choose New host (A and AAAA)...

1884752b-4c2a-4d63-8f94-e30e36fb1136 

9. Create a new host record, leaving the Name field blank and entering the LAN IP address of the MX in the IP address field. You do not need to create a PTR record so deselect this box. Click Add host.

a0afb1b4-8a5b-4441-b9e9-08805466277d

10. Now the A record will appear in the zone. 

52711da1-cd47-4873-9784-6e6364e516d4

You must to post a comment.
Last modified
22:08, 2 Feb 2015

Tags

Classifications

This page has no classifications.

Explore Meraki

You can find out more about Cisco Meraki on our main site, including information on products, contacting sales and finding a vendor.

Explore Meraki

Contact Support

Most questions can be answered by reviewing our documentation, but if you need more help, Cisco Meraki Support is ready to work with you.

Open a Case

Ask the Community

In the Meraki Community, you can keep track of the latest announcements, find answers provided by fellow Meraki users and ask questions of your own.

Visit the Community