{"_id":"57f2c3f964c01c2d00f811da","parentDoc":null,"category":{"_id":"56a938862036420d002d23a4","version":"56a938852036420d002d23a3","__v":3,"pages":["56a938872036420d002d23a6","56abf9759327b30d00f7c2a5","56afa3529ca3b20d0017571a"],"project":"56a938852036420d002d23a0","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-01-27T21:37:10.291Z","from_sync":false,"order":0,"slug":"documentation","title":"Documentation"},"project":"56a938852036420d002d23a0","user":"560b40145148ba0d009bd0b5","__v":1,"version":{"_id":"56a938852036420d002d23a3","__v":1,"project":"56a938852036420d002d23a0","createdAt":"2016-01-27T21:37:09.719Z","releaseDate":"2016-01-27T21:37:09.719Z","categories":["56a938862036420d002d23a4"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-10-03T20:47:53.689Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"settings":"","results":{"codes":[]},"auth":"required","params":[],"url":""},"isReference":false,"order":3,"body":"## Introduction\n\nAs the administrator of a Meraki Device, you are able to connect to the free and fast Cisco Umbrella global network DNS service which will offer you visibility into all internet traffic originating from your Meraki device and result in a faster internet experience for your users. If you then want to add an additional layer of DNS security to your Meraki device, the easy-to-establish connection to Umbrella enables you to access our free tria—which you can setup (by yourself) in less than five minutes. \n\n## Using the Cisco Umbrella global network's DNS Services\n\nUmbrella is a leading provider of network security and DNS services, enabling the world to connect to the Internet with confidence on any device, anywhere, anytime. The Umbrella cloud-delivered network security service blocks command & control callbacks, malware, and phishing from compromising systems and exfiltrating data over any port, protocol, or app. We apply statistical models to real-time and historical DNS data to predict domains that are likely malicious and could be used in future attacks. Umbrella protects all devices globally without hardware to install or software to maintain. Umbrella has data centers across all regions of the world to ensure that the first hop to the service is as fast as possible.\n\nThis document covers how to configure the Meraki network to use the Umbrella IP addresses of 208.67.222.222 and 208.67.220.220. \n\nAdditionally, if you are using a DNS forwarder as the primary DNS server for your network, this document covers how to update Windows 2003 Server, Windows 2008 Server, Windows 2012 Server or BIND Server to use Umbrella.\n\nOnce you’ve configured your Meraki infrastructure to point to Umbrella, you can sign up for either a free premium DNS account or a free 14-day trial of Umbrella.\n\n####Free Premium DNS\nWe offer a free, fast recursive DNS service which gives you visibility into all of your [Internet traffic originating from your Meraki device](https://store.opendns.com/premiumdns/?utm_source=meraki&utm_medium=ciscopartner&utm_campaign=meraki-guide-free-trial-home).\n\n####Free Umbrella 14-Day Trial\nIf you want to add an additional layer of DNS security, try our free trial—you can set it up yourself in less than five minutes. Sign up at umbrellla.com today!\n\n## Setting up Umbrella for a Meraki network\n\nThere are two ways in which you can configure your Meraki networks to use Umbrella. The first is to use DHCP to distribute the Umbrella server IP information directly to clients. This is available on all Meraki platforms. The second method, available only on MX Security Appliances and Z1 Teleworker Gateways, is to configure the MX itself to use the Umbrella servers and to proxy client DNS requests to those same servers.\n\n### How to configure Umbrella for clients\n\n**For MX Security Appliances:** From your cloud dashboard, select **Security Appliance > Configure > DHCP**. Under the DHCP scope you wish to configure, choose _Use OpenDNS_ from the DNS nameservers drop-down list. DHCP must be enabled for the desired subnet for this option to appear.\n\n**For MS Switches:** From your cloud dashboard, select **Switch > Configure > Routing and DHCP**. Select the route you wish to modify the DHCP service for, and choose _Use OpenDNS_ from the DNS nameservers drop-down list under DHCP Settings. DHCP must be enabled for the desired subnet for this option to appear. For more information on how to configure the DHCP server for MX Security Appliances and MS Switches, please see [Configuring DHCP Services on the MX and MS](http://documentation.meraki.com/MS/Layer_3_Switching/Configuring_DHCP_Services_on_the_MX_and_MS).\n\n**For MR Access Points (NAT Mode SSIDs only):** From your cloud dashboard, select **Wireless > Configure > Access Control**. Select the SSID you wish to configure, and select Custom DNS from the Content filtering drop-down under Addressing and Traffic. Enter in the Umbrella server IP addresses: **208.67.222.222** and **208.67.220.220.**\n\n### How to configure your Meraki network to proxy DNS to Umbrella\n(MX Security Appliance and Z1 Teleworker Gateway only)\n\n**Note:** Static IP configuration for the MX and Z1 devices must be performed locally and cannot be done through the cloud dashboard. Once logged into the local status page, browse to the Uplink Configuration page and configure the DNS settings to use 208.67.222.222 and 208.67.220.220 under IP Assignment. This method can only be used with Static IP addressing.\nFor more information on how to access the local configuration, please see\n[Using the Cisco Meraki Device Local Status Page](https://docs.meraki.com/display/MX/MX+Local+Status+and+Configuration).\n\nFrom your cloud dashboard, select **Security Appliance > Configure > DHCP.** Under DNS nameservers select Proxy to upstream DNS.\n\n## Configuring your DNS forwarder for Umbrella\n\nEven with a Cisco or Meraki device in place at the gateway or egress, DNS for networks is often handled by DNS forwarders installed on DNS servers within the network environment. A DNS forwarder is a DNS server on a network that forwards DNS queries for external domain names to the Umbrella servers. A DNS server on a network is designated as a forwarder when the other DNS servers in the network are configured to forward the queries that they cannot resolve\nlocally to that DNS server.\nThe following instructions cover how to configure your DNS forwarder to use the Umbrella public DNS servers for BIND and Windows Server 2003, 2008 and 2012.\n\n### Windows Server 2003 and 2003 R2\n\n1. From the Start menu, navigate to **Administrative Tools > DNS**.\n2. Choose the DNS server you want to edit.\n3. Select Forwarders.\n4. Select All Other DNS domains in the DNS domains list.\n5. Add Umbrella's addresses to the selected server’s forwarder IP address list.\n\n Write down your current DNS settings before switching to Umbrella. This will help you if you ever need to return to your old settings.\n\n Umbrella’s addresses are 208.67.222.222 and 208.67.220.220.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/rZUdyt3PSsqXJigQkITg_2003-server.png\",\n        \"2003-server.png\",\n        \"450\",\n        \"372\",\n        \"#fa7626\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\n6. Click **OK** to confirm the changes.\n\nWe recommend that you flush the DNS resolver cache of the server and the DNS caches of the clients/users using the DNS server to ensure that your new DNS configuration settings take\nimmediate effect.\n\n### Windows Server 2008 and 2008 R2\n1. From the Start menu, navigate to **Administrative Tools > DNS**.\n2. Choose the DNS server you want to edit.\n3. Select **Forwarders**.\n4. Click **Edit**.\n5. Add Umbrella addresses in the selected server’s forwarder IP address list.\n\n Write down your current DNS settings before switching to Umbrella. This will help you if you ever need to return to your old settings.\n\n Umbrella’s addresses are 208.67.222.222 and 208.67.220.220.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/1rJ8l5ZATBqvf9X7pCJY_2008.png\",\n        \"2008.png\",\n        \"695\",\n        \"217\",\n        \"#3d4f75\",\n        \"\"\n      ],\n      \"sizing\": \"80\"\n    }\n  ]\n}\n[/block]\n6. Click **OK**.\n7. Click **OK** again to confirm the changes.\n\nWe recommend that you flush the DNS resolver cache of the server and the DNS caches of the clients/users using the DNS server to ensure that your new DNS configuration settings take immediate effect.\n\n### Windows Server 2012 and 2012 R2\n1. In the **Start** menu, type DNS into **Search**.\n2. Select DNS from the search results.\n3. Choose the DNS server you want to edit.\n4. Select **Forwarders**.\n5. Click **Edit**.\n6. Add Umbrella's addresses to the selected server’s forwarder IP address list.\n\n Write down your current DNS settings before switching to Umbrella. This will help you if you ever need to return to your old settings.\n\n Umbrella’s addresses are 208.67.222.222 and 208.67.220.220.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/NfxofWT3TaG97zj31nLU_2012.png\",\n        \"2012.png\",\n        \"538\",\n        \"448\",\n        \"#689456\",\n        \"\"\n      ],\n      \"sizing\": \"80\"\n    }\n  ]\n}\n[/block]\n7. Click **OK**.\n8. Click **OK** again to confirm the changes\n\n### BIND-based DNS server: Configure BIND to use Umbrella via the shell and Webmin\n\nTo point your BIND-based DNS server to use Umbrella resolvers for external resolution you need to modify the file named.conf.options and add the Umbrella resolvers as forwarders. This can be done in one of two ways:\n• Via the command line, Shell\\SSH\n• Via a GUI if you have Webmin installed on your BIND server\n\n*Shell\\SSH Instructions*\n1. Connect directly to your server or SSH to it.\n2. Go into /etc/bind.\n*Note:* this is the default location, so you may need to change this based on your configuration.\n3. Edit named.conf.options in your favorite text editor.\n4. Click **Edit**.\n5. In named.conf.options, look for a line that starts with forwarders {\nIf the forwarders are already configured then just change the current resolver IPs to Umbrella's IP addresses, which are 208.67.222.222 and 208.67.220.220. If the line starting with \"forwarders {\" isn’t there, you can add it right above the last };\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"forwarders {\\n208.67.222.222;\\n208.67.220.220;\\n};\",\n      \"language\": \"text\"\n    }\n  ]\n}\n[/block]\n6. Save the file to confirm your changes.\n\n####Webmin Instructions\n\nThese steps produce a result that is the exact same as the above, except that the Webmin GUI modifies the file named.conf.options for you.\n\n1. Log into Webmin.\n2. Navigate to **Servers > BIND DNS Server.**\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/Up1G3tzTra5FH3l0erc8_webmin1.png\",\n        \"webmin1.png\",\n        \"382\",\n        \"130\",\n        \"#3a3e77\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\n3. Choose **Forwarding and Transfers**.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/chMzxUzQwulneR5suLrQ_webmin2.png\",\n        \"webmin2.png\",\n        \"368\",\n        \"140\",\n        \"#5f60a1\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\n4. Add Umbrella's IP addresses—208.67.222.222 and 208.67.220.220—under the **Servers to forward queries to** section.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/moYG2ovnQMuvhNm3AV2f_webmin3.png\",\n        \"webmin3.png\",\n        \"907\",\n        \"262\",\n        \"#4b78b9\",\n        \"\"\n      ],\n      \"sizing\": \"80\"\n    }\n  ]\n}\n[/block]\n5. Click **Save** to confirm the changes.\n\n\n---\n[Integration for ISR G2 – Solution Guide for Umbrella](https://docs.umbrella.com/product/hardware/cisco-integrated-services-router-g2-isr-solution-guide-for-umbrella/) < **Meraki Cloud-Managed Networks – Solution Guide for Umbrella** > [Integration for ASA – Solution Guide for Umbrella](https://docs.umbrella.com/product/hardware/cisco-adaptive-security-appliance-asa-solution-guide-for-umbrella/)","excerpt":"","slug":"meraki-cloud-managed-networks-umbrella-solution-guide","type":"basic","title":"Meraki Cloud-Managed Networks – Solution Guide for Umbrella"}

Meraki Cloud-Managed Networks – Solution Guide for Umbrella


## Introduction As the administrator of a Meraki Device, you are able to connect to the free and fast Cisco Umbrella global network DNS service which will offer you visibility into all internet traffic originating from your Meraki device and result in a faster internet experience for your users. If you then want to add an additional layer of DNS security to your Meraki device, the easy-to-establish connection to Umbrella enables you to access our free tria—which you can setup (by yourself) in less than five minutes. ## Using the Cisco Umbrella global network's DNS Services Umbrella is a leading provider of network security and DNS services, enabling the world to connect to the Internet with confidence on any device, anywhere, anytime. The Umbrella cloud-delivered network security service blocks command & control callbacks, malware, and phishing from compromising systems and exfiltrating data over any port, protocol, or app. We apply statistical models to real-time and historical DNS data to predict domains that are likely malicious and could be used in future attacks. Umbrella protects all devices globally without hardware to install or software to maintain. Umbrella has data centers across all regions of the world to ensure that the first hop to the service is as fast as possible. This document covers how to configure the Meraki network to use the Umbrella IP addresses of 208.67.222.222 and 208.67.220.220. Additionally, if you are using a DNS forwarder as the primary DNS server for your network, this document covers how to update Windows 2003 Server, Windows 2008 Server, Windows 2012 Server or BIND Server to use Umbrella. Once you’ve configured your Meraki infrastructure to point to Umbrella, you can sign up for either a free premium DNS account or a free 14-day trial of Umbrella. ####Free Premium DNS We offer a free, fast recursive DNS service which gives you visibility into all of your [Internet traffic originating from your Meraki device](https://store.opendns.com/premiumdns/?utm_source=meraki&utm_medium=ciscopartner&utm_campaign=meraki-guide-free-trial-home). ####Free Umbrella 14-Day Trial If you want to add an additional layer of DNS security, try our free trial—you can set it up yourself in less than five minutes. Sign up at umbrellla.com today! ## Setting up Umbrella for a Meraki network There are two ways in which you can configure your Meraki networks to use Umbrella. The first is to use DHCP to distribute the Umbrella server IP information directly to clients. This is available on all Meraki platforms. The second method, available only on MX Security Appliances and Z1 Teleworker Gateways, is to configure the MX itself to use the Umbrella servers and to proxy client DNS requests to those same servers. ### How to configure Umbrella for clients **For MX Security Appliances:** From your cloud dashboard, select **Security Appliance > Configure > DHCP**. Under the DHCP scope you wish to configure, choose _Use OpenDNS_ from the DNS nameservers drop-down list. DHCP must be enabled for the desired subnet for this option to appear. **For MS Switches:** From your cloud dashboard, select **Switch > Configure > Routing and DHCP**. Select the route you wish to modify the DHCP service for, and choose _Use OpenDNS_ from the DNS nameservers drop-down list under DHCP Settings. DHCP must be enabled for the desired subnet for this option to appear. For more information on how to configure the DHCP server for MX Security Appliances and MS Switches, please see [Configuring DHCP Services on the MX and MS](http://documentation.meraki.com/MS/Layer_3_Switching/Configuring_DHCP_Services_on_the_MX_and_MS). **For MR Access Points (NAT Mode SSIDs only):** From your cloud dashboard, select **Wireless > Configure > Access Control**. Select the SSID you wish to configure, and select Custom DNS from the Content filtering drop-down under Addressing and Traffic. Enter in the Umbrella server IP addresses: **208.67.222.222** and **208.67.220.220.** ### How to configure your Meraki network to proxy DNS to Umbrella (MX Security Appliance and Z1 Teleworker Gateway only) **Note:** Static IP configuration for the MX and Z1 devices must be performed locally and cannot be done through the cloud dashboard. Once logged into the local status page, browse to the Uplink Configuration page and configure the DNS settings to use 208.67.222.222 and 208.67.220.220 under IP Assignment. This method can only be used with Static IP addressing. For more information on how to access the local configuration, please see [Using the Cisco Meraki Device Local Status Page](https://docs.meraki.com/display/MX/MX+Local+Status+and+Configuration). From your cloud dashboard, select **Security Appliance > Configure > DHCP.** Under DNS nameservers select Proxy to upstream DNS. ## Configuring your DNS forwarder for Umbrella Even with a Cisco or Meraki device in place at the gateway or egress, DNS for networks is often handled by DNS forwarders installed on DNS servers within the network environment. A DNS forwarder is a DNS server on a network that forwards DNS queries for external domain names to the Umbrella servers. A DNS server on a network is designated as a forwarder when the other DNS servers in the network are configured to forward the queries that they cannot resolve locally to that DNS server. The following instructions cover how to configure your DNS forwarder to use the Umbrella public DNS servers for BIND and Windows Server 2003, 2008 and 2012. ### Windows Server 2003 and 2003 R2 1. From the Start menu, navigate to **Administrative Tools > DNS**. 2. Choose the DNS server you want to edit. 3. Select Forwarders. 4. Select All Other DNS domains in the DNS domains list. 5. Add Umbrella's addresses to the selected server’s forwarder IP address list. Write down your current DNS settings before switching to Umbrella. This will help you if you ever need to return to your old settings. Umbrella’s addresses are 208.67.222.222 and 208.67.220.220. [block:image] { "images": [ { "image": [ "https://files.readme.io/rZUdyt3PSsqXJigQkITg_2003-server.png", "2003-server.png", "450", "372", "#fa7626", "" ] } ] } [/block] 6. Click **OK** to confirm the changes. We recommend that you flush the DNS resolver cache of the server and the DNS caches of the clients/users using the DNS server to ensure that your new DNS configuration settings take immediate effect. ### Windows Server 2008 and 2008 R2 1. From the Start menu, navigate to **Administrative Tools > DNS**. 2. Choose the DNS server you want to edit. 3. Select **Forwarders**. 4. Click **Edit**. 5. Add Umbrella addresses in the selected server’s forwarder IP address list. Write down your current DNS settings before switching to Umbrella. This will help you if you ever need to return to your old settings. Umbrella’s addresses are 208.67.222.222 and 208.67.220.220. [block:image] { "images": [ { "image": [ "https://files.readme.io/1rJ8l5ZATBqvf9X7pCJY_2008.png", "2008.png", "695", "217", "#3d4f75", "" ], "sizing": "80" } ] } [/block] 6. Click **OK**. 7. Click **OK** again to confirm the changes. We recommend that you flush the DNS resolver cache of the server and the DNS caches of the clients/users using the DNS server to ensure that your new DNS configuration settings take immediate effect. ### Windows Server 2012 and 2012 R2 1. In the **Start** menu, type DNS into **Search**. 2. Select DNS from the search results. 3. Choose the DNS server you want to edit. 4. Select **Forwarders**. 5. Click **Edit**. 6. Add Umbrella's addresses to the selected server’s forwarder IP address list. Write down your current DNS settings before switching to Umbrella. This will help you if you ever need to return to your old settings. Umbrella’s addresses are 208.67.222.222 and 208.67.220.220. [block:image] { "images": [ { "image": [ "https://files.readme.io/NfxofWT3TaG97zj31nLU_2012.png", "2012.png", "538", "448", "#689456", "" ], "sizing": "80" } ] } [/block] 7. Click **OK**. 8. Click **OK** again to confirm the changes ### BIND-based DNS server: Configure BIND to use Umbrella via the shell and Webmin To point your BIND-based DNS server to use Umbrella resolvers for external resolution you need to modify the file named.conf.options and add the Umbrella resolvers as forwarders. This can be done in one of two ways: • Via the command line, Shell\SSH • Via a GUI if you have Webmin installed on your BIND server *Shell\SSH Instructions* 1. Connect directly to your server or SSH to it. 2. Go into /etc/bind. *Note:* this is the default location, so you may need to change this based on your configuration. 3. Edit named.conf.options in your favorite text editor. 4. Click **Edit**. 5. In named.conf.options, look for a line that starts with forwarders { If the forwarders are already configured then just change the current resolver IPs to Umbrella's IP addresses, which are 208.67.222.222 and 208.67.220.220. If the line starting with "forwarders {" isn’t there, you can add it right above the last }; [block:code] { "codes": [ { "code": "forwarders {\n208.67.222.222;\n208.67.220.220;\n};", "language": "text" } ] } [/block] 6. Save the file to confirm your changes. ####Webmin Instructions These steps produce a result that is the exact same as the above, except that the Webmin GUI modifies the file named.conf.options for you. 1. Log into Webmin. 2. Navigate to **Servers > BIND DNS Server.** [block:image] { "images": [ { "image": [ "https://files.readme.io/Up1G3tzTra5FH3l0erc8_webmin1.png", "webmin1.png", "382", "130", "#3a3e77", "" ] } ] } [/block] 3. Choose **Forwarding and Transfers**. [block:image] { "images": [ { "image": [ "https://files.readme.io/chMzxUzQwulneR5suLrQ_webmin2.png", "webmin2.png", "368", "140", "#5f60a1", "" ] } ] } [/block] 4. Add Umbrella's IP addresses—208.67.222.222 and 208.67.220.220—under the **Servers to forward queries to** section. [block:image] { "images": [ { "image": [ "https://files.readme.io/moYG2ovnQMuvhNm3AV2f_webmin3.png", "webmin3.png", "907", "262", "#4b78b9", "" ], "sizing": "80" } ] } [/block] 5. Click **Save** to confirm the changes. --- [Integration for ISR G2 – Solution Guide for Umbrella](https://docs.umbrella.com/product/hardware/cisco-integrated-services-router-g2-isr-solution-guide-for-umbrella/) < **Meraki Cloud-Managed Networks – Solution Guide for Umbrella** > [Integration for ASA – Solution Guide for Umbrella](https://docs.umbrella.com/product/hardware/cisco-adaptive-security-appliance-asa-solution-guide-for-umbrella/)