---
title: "Deploying DNS Forwarding Proxy"
canonical: "https://docs.infoblox.com/space/BloxOneThreatDefense/257885719/Deploying%20DNS%20Forwarding%20Proxy"
format: markdown
---
You can deploy DFP (DNS Forwarding Proxy) as a service on physical appliances, virtual appliances, and NIOS Grid members. To deploy a DFP, you first set up a NIOS-X server, and then create a DFP service instance and apply it to the server. 

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 the Infoblox Platform. For more information, see *[Creating DNS Forwarding Proxy Services](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneInfrastructure/pages/166068707)* and *[Configuring Templates](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneInfrastructure/pages/149160274)*.

> 📝 NIOS-X allows configuration updates to be applied sequentially on NIOS-X servers, even when you schedule software updates. Configuration updates are performed one NIOS-X server at a time, progressing to the next server only after the configuration on the current server has been updated successfully. For information, see *[Scheduling Configuration Updates for Servers](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneInfrastructure/pages/184583817)*.

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.
- **Application Filters**: When an application filter is configured with "**Allow Local Resolution**" in a policy, the DFP associated with that policy must be set to use an internal resolver. This ensures that domains are resolved locally using the configured internal resolvers of the DFP.
- **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:

- *[Firewall Requirements for Infoblox Cloud Services](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneInfrastructure/pages/873660456)*
- *[Minimum System Requirements for NIOS-X Servers](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneInfrastructure/pages/873758806)*
- *[Supported Platforms for NIOS-X Servers](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneInfrastructure/pages/873693279)*
- *[Port Usage for Bare-Metal NIOS-X Servers](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneInfrastructure/pages/873758860)*
- *[Best Practices for Deploying NIOS-X Servers](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneInfrastructure/pages/204538456)*

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

> Macro (children)