Lumu Virtual Appliance (VA) offers a seamless way to integrate the network metadata of your entire enterprise into the Lumu platform. You can easily deploy and set up a Lumu Virtual appliance to collect DNS network metadata through the Virtual Appliances section of the portal. For this, you need to configure your devices to point all DNS requests to Lumu the Virtual Appliance’s IP addresses, substituting the automatic DNS servers provided by your internet service provider (ISP).
By default, the primary and secondary DNS Server fields of the Lumu VA are already populated with public DNS Servers, which is adequate for most small networks. However, if you have local primary and secondary DNS servers, you should specify your DNS servers accordingly. You can manage these settings using the command.
In the forward zones settings, you have the option to specify if you plan to use TLS (Transport Layer Security). If you use TLS, you should set the DNS addresses in the following format:
We recommend doing this procedure on your edge DNS equipment, typically a router, DNS, or DHCP server in your company. Commonly, 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.
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: