Point your DNS to Lumu’s DNS servers to start illuminating threats

Point your DNS to Lumu

To start taking advantage of Lumu — depending on your deployment scenario — need to configure your devices to point all DNS requests to Lumu's DNS revolvers’ IP or your Virtual Appliance’s IP addresses, substituting the automatic DNS servers provided by your internet service provider (ISP).

Once you have pointed your DNS to Lumu, all the requests to resolve a hostname on the internet will be processed by Lumu against its proprietary intelligence including machine learning and artificial intelligence models to identify if your network is “talking” with adversarial infrastructure.
Enterprise perimeter pointing DNS to LumuFigure 1 - Enterprise perimeter pointing DNS to Lumu.
Configuring your DNS

We recommend doing this procedure on your edge DNS equipment , typically a router, DNS, or DHCP server in your company. Typically, the device that provides an internal non-routable IP address (DHCP) or the device that serves as your default gateway is also where you configure public DNS servers.  Most often this will be a DNS server or a router—this might be your DSL router or cable modem if that is the only router in your network.

Remember to first  register your public IP address or group of IPs as a gateway  for your company at the Lumu Portal before configuring your DNS.
In the following video we guide you on how to configure your internal DNS to use our DNS resolvers in the management console of a Windows DNS server:


Before you change your DNS settings to use Lumu Gateways’, be sure to record the current DNS server addresses. It's important that you keep this data for backup purposes—just in case you need to revert to them at a later date.

Some ISPs hard-code their DNS servers into the equipment they provide. If you are using such a device, you will not be able to configure it to use Lumu. Instead, you can configure each one of your devices (desktops, servers, etc).

The process for changing your DNS settings varies according to the operating system (OS) and versions (Windows, Mac, or Linux) or the device (desktop, DNS server, router, or mobile device). For authoritative information, please consult the vendor documentation. We have created the following guides to help you with this configuration:

        • Related Articles

        • Validate your DNS Settings

          Now that you have already configured your DNS traffic to be routed through Lumu, check that your DNS connections are working as expected. Please note that this procedure is only valid when setting Lumu Gateways. When you make changes to DNS settings, ...
        • Add a Public Gateway

          With Lumu public gateways you can start associating all the traffic originating from your organization with Lumu’s DNS servers for illuminating threats, attacks, and adversaries coming from your network. If you want more context on Lumu deployment ...
        • Apple macOS

          Setting up a Lumu Gateway on a macOS device is the configuration recommended for testing purposes as we recommend you configure your server or your router to take the most advantage of the Lumu Continuous Compromise Assessment on your entire network. ...
        • Windows 10

          Setting up Lumu on a Windows client device is the configuration recommended for testing purposes as we recommend you configure your server or your router to take the most advantage of the Lumu Continuous Compromise Assessment on your entire network. ...
        • Linux Desktop

          Setting up Lumu Gateway on a Linux client device is the configuration recommended for testing purposes as we recommend you configure your server or your router to take the most advantage of Lumu Continuous Compromise Assessment on your entire ...