You can deploy DFP as a service on physical appliances, virtual appliances, and NIOS Grid members. To deploy a DFP, you first set up an Infoblox host, and then create a DFP service instance and apply it to the host. You can also use an exiting service template and apply the template to the host. Once you set up the DFP, DNS queries are sent directly to Infoblox Platform. For more information, see Creating DNS Forwarding Proxy Services and Configuring Templates.

While setting up the DFP service instance, you can define the following based on your business needs:

Internal Resolvers: An internal resolver is a local DNS server that stores a central database of DNS name servers and manages DNS requests for all clients on your network. You can add internal resolvers for situations where connection between the DFP and Infoblox Platform is lost of if Infoblox DNS fails to resolve DNS requests.
Internal Domain Lists: If you have internal domains that are served by local DNS servers and you want to reach them without interruptions, you should consider adding them to the bypassed internal domains list. If you add them, DNS queries for these internal domains are sent to the local DNS servers instead of Infoblox Platform.
Point of Presence: The DNS service typically resolves and directs traffic through the closest PoP rather than through the one closest to the requesting location, which might result in longer latency and slower application response times. For performance reasons, you can choose a preferred PoP based in a specific region..

Before Deploying DFP

Before you deploy a DFP, ensure that you review the following:

Depending on your network infrastructure, you can choose one or all of the following options to deploy a DFP:

BloxOne Threat Defense

Deploying DNS Forwarding Proxy

Before Deploying DFP