Topic
This article provides best practices for configuring DNS in ControlOne.
Environment
- Cytracom ControlOne
Description
Zone DNS settings
Accessing DNS settings
1. In the Network Map, click the Zone to which the DNS settings will apply.
2. The Configuration Options panel will open on the right-hand side of the screen. Click the DNS tab.
Recommended DNS settings
Cytracom recommends the following DNS settings for general use:
- Mode: Auto
- Advanced: Cytracom recommends using the Auto setting for most applications.
You do not need to enter a DNS server primary or secondary address the way you would on other types of networking equipment. ControlOne assigns these addresses automatically.
If your environment requires a specified DNS server entry, contact Cytracom Technical Support for assistance. DHCP Option 6 can be enabled to use alternate DNS servers for connected devices but is not recommended. See DHCP Option 6 and third-party DNS servers, below.
- Advanced Gateway: leave unchecked.
Figure 1: Recommended DNS settings (click to enlarge)
ControlOne and internal DNS servers
If you currently have a DNS server on your network Cytracom recommends a hybrid approach, in which:
- Your DNS server handles DNS for resources on your domain.
- The ControlOne bridge handles DNS requests for public resources.
You can set this configuration up in the ControlOne Portal using conditional forwards.
Conditional forwards
A DNS Conditional forward is a setting on the ControlOne Bridge that forwards all DNS requests for a specific DNS domain to the authoritative server of your choosing.
For example, if you have a local domain controller running DNS service with zones for 'yourcompany.local', a conditional forward will instruct ControlOne to forward any DNS lookups for that domain to your local domain controller. This gives you the best combination of DNS functionality, allowing fast global DNS resolution and local domain resolution. See Cytracom ControlOne: Conditional forwards to learn more.
Figure 2: Conditional forward flow on a ControlOne Bridge (click to enlarge)
DHCP Option 6 and third-party DNS servers
DHCP Option 6 tells the devices in a zone to send their DNS lookups to a server you choose instead of the ControlOne bridge. It works, but devices that skip the bridge for DNS lose the following:
- Conditional forwards and static records: These are set on the bridge. A device that asks another DNS server never sees them, so names on your domain may not resolve the way you set them up in the portal.
- Local caching: In Auto mode, the bridge caches answers on site, so repeat lookups are answered without leaving the network.
- Malicious domain blocking at the resolver: In Auto mode, the bridge sends lookups to public resolvers that also block known malware and phishing domains.
ControlOne DNS & Content Filtering
You don't need a third-party DNS filtering service with ControlOne. DNS & Content Filtering is part of the zone's security policy, and the categories you choose there are applied to both DNS lookups and web traffic. You manage them in one place in the portal. See Cytracom ControlOne: Content filtering levels.
Adding a third-party DNS filter on top of ControlOne usually causes more problems than it solves:
- Two sets of rules: A site can be allowed in ControlOne and blocked by the other service, or the other way around, so you have to check both places to find out why a site won't load.
- A different public IP address: Internet traffic from a ControlOne site reaches the Internet from the ControlOne cloud, not from your office's own public IP address. A DNS filtering service that identifies your site by its public IP address won't recognize your traffic.
- Encrypted DNS: Some third-party DNS clients encrypt their lookups. ControlOne's DNS filter can't read those, so those devices are only covered by web filtering.
If devices need a specific DNS server
- For your own domain (for example, a domain controller): Keep the bridge as the DNS server and add a conditional forward for your domain, as described above. You don't need Option 6 for this.
- For all lookups: If a requirement means devices must use another DNS server, you can add DHCP Option 6 to the zone with up to 3 servers, comma-separated with no spaces. See Cytracom ControlOne: Configuring DHCP options. Make sure the servers you list can also resolve your internal names, since conditional forwards on the bridge won't apply.
Questions about which approach fits your network? Reach out to the ControlOne support team.
DNS and the ControlOne Agent
The ControlOne Agent is a full-tunnel connectivity solution. All Internet traffic is sent up the tunnel to the Cytracom platform. Traffic to devices on the network behind the bridge is tunneled to those locations, and all other Internet traffic is directly sent up from the cloud-based firewall.
- DNS queries for all Internet-based resources are handled by our fast caching-resolving nameservers.
- DNS queries for on-prem devices advertised via local DNS servers are sent (via Conditional Forward) to those servers.
If you log in using the ControlOne Agent, make sure the agent can reach the resources within your site zones. The agent must be able to reach your site zone resources before it will successfully log you in.
Figure 3: DNS and the ControlOne Agent (click to enlarge)