To access the BloxOne Cloud Infoblox Platform DNS service, you must forward your DNS traffic (except for internal domain resolution) to the BloxOne Cloud Infoblox Platform name server. In essence, a DNS forwarder is a name server to which all other name servers first send queries that they cannot resolve locally. The forwarder then sends these queries to DNS servers external to the network, and this saves the other name servers in your network from having to send queries off site. A forwarder eventually builds up a cache of information and uses it to resolve queries. This reduces Internet traffic over the network and decreases the time taken to respond to DNS clients.

...

• External Networks

• DFP (DNS Forwarding Proxy) (either standalone or running on NIOS)

• BloxOne Endpoint or BloxOne Mobile Endpoint

The manner in which you configure your DNS forwarders to use the BloxOne Infoblox Threat Defense name server depends on your network configuration:

• If you have an on-prem Infoblox Grid, configure your Grid members (which act as DNS forwarders) to use the BloxOne Infoblox Threat Defense name server.

• If you are using Unbound, BIND, or any other third-party DNS server as your DNS resolver, then, in your DNS configuration file, configure your DNS forwarders to use the BloxOne Infoblox Threat Defense name server IP.

• You can also configure Microsoft servers to use DNS forwarders. 

• In corporate mode, BloxOne Infoblox Endpoint supports transfer of metadata to BloxOne Cloud Infoblox Platform when queries are resolved by DFP.

If you are forwarding DNS traffic to the BloxOne Infoblox Threat Defense name servers using the External Networks configuration, without BloxOne Infoblox Endpoint or DFP, you should provision the following DNS anycast addresses:

...

• Connectivity Rules for DNS Forwarding Proxy

• DNS Forwarding Proxy Fallback to Local DNS Server

Infoblox Geo-Based Anycast IPs for POPs

Infoblox-provided anycast addresses (listed above) will route your DNS traffic to the appropriate PoPs.

If you want to direct DNS traffic to a specific location, you can use the geo-based anycast IPs listed in the following table.

Local DNS Request Processing Optimization

To reduce the number of noise requests forwarded to the cloud and to avoid misconfiguration, DFP and BloxOne Infoblox Endpoint will automatically forward all PTR requests for any private subnets (e.g. 10.0.0.0/8, 192.168.0.0/16, etc.) to local DNS servers. With this enhancement, you will not need to list such subnets in the internal domains or custom allow lists.

...