BloxOne provides DNS fallback mechanisms to ensure DNS protection for your networks in cases where your local DNS resolver is temporarily offline or when the connection from your BloxOne hosts to BloxOne Cloud is unavailable. When you enable DNS fallback, your BloxOne system will always have a functional name server to fall back to, so your DNS queries can always be resolved.
Depending on your network setup, you can enable DNS fallback when you configure DFP (DNS Forwarding Proxy) settings via the Cloud Services Portal or setting up DFP on NIOS.
DFP Settings via the Cloud Services Portal
To enable DNS fallback on a DFP service in the Cloud Services Portal:
- Log in to the Cloud Services Portal
- Go to Manage > Infrastructure > Services.
- Select the DFP service on which you want to configure DNS fallback, and then click Edit.
- Click the DNS Forwarding Proxy tab and expand the Internal and Fallback Local Resolvers section.
- Click Add and add to the table the FQDN or IP address of the fallback DNS server.
- Enable the Fallback Resolver option for the fallback address.
- Click Next.
- Click Save & Close.
For information about DFP fallback to local DNS server and health checks, see DNS Forwarding Proxy Fallback to Local DNS Server.
DFP on NIOS Settings via the Grid Manager
To configure DNS fallback using DFP on NIOS:
- Log in to the NIOS Grid Manager UI.
- Select a Grid member and navigate to Grid Member > DFP Properties.
- Select the Fallback to the default resolution process if BloxOne Threat Defense cloud does not respond check box.
When you select the check box, the DNS queries will fall back to the root server(s) even if there are forwarders added at the DNS member level. If you cannot enable the root servers or if the root servers are not reachable, ensure that you use DNS protection by enabling Fallback Resolver when configuring the applicable DFP service, so the DNS queries will fall back to the configured server(s). For information, see Configuring DNS Forwarding Proxy Settings.