| Warning |
|---|
Important NoteThe minimum system requirements specified for NIOS-X server deployment must be dedicated to the server you plan to deploy. They cannot be shared with or used for other non-Infoblox applications. Sharing resources will negatively affect the performance of your Infoblox services. For more information, see Minimum System Requirements for Servers. Before you deploy Infoblox services and servers, ensure that you prepare your environment according to the requirements for the supported platforms and open all necessary ports for unrestricted outbound access. All used IPs on the provided list require TCP 443 to be open when in use. |
Port Usage for Server Connectivity
For NIOS-X server connectivity to function properly, ensure that the following are in place:
...
Source | Destinations | Destination IPs | Protocol | Destination | Description |
|---|---|---|---|---|---|
Universal DDI | US Region
EU Region
| US Region dns.bloxone.infoblox.com
csp.infoblox.com
cp.noa.infoblox.com
grpc.csp.infoblox.com
app.noa.infoblox.com
EU Region dns.bloxone.eu.infoblox.com
csp.eu.infoblox.com
cp.noa.eu.infoblox.com
app.noa.eu.infoblox.com
| TCP | 443 | Allow these IP addresses on the firewall for the NIOS-X servers to connect to the Infoblox Portal, and to ensure BloxOne Universal DDI services function properly in the respective regions. |
NIOS-X Servers DNS Forwarding Proxy | threatdefense.bloxone.infoblox.com threatdefense.infoblox.com (and all subdomains) Note: Communication with these destinations will bypass any proxy server setting. In other words, if you configure a proxy, the DNS forwarding proxy service (threatdefense.bloxone.infoblox.com:443) is bypassed on the proxy. If you configure a proxy, the BloxOne Universal DDI service destination (dns.bloxone.infoblox.com:443) is bypassed on the proxy. | Anycast IPs (IPv4 and IPv6)
For geo-specific IP addresses, refer to the Infoblox geo-based Anycast IPs for POPs table in Forwarding DNS Traffic to BloxOne CloudInfoblox Platform. | TCP | 443 53 | BloxOne Infoblox uses 52.119.40.100 as the default local resolver for all NIOS-X servers. However, you can use your own local resolver to resolve the destination domains. |
NIOS-X Servers | US Region
EU Region
| A complete list of the used IP addresses is available in a JSON file by clicking this link. | TCP | 443 | All listed IPs require TCP 443 port be open when being used. |
End Client | N/A | Redirect IPs: For IPv4:
For IPv6:
| TCP | 443 or 80 | For redirect purposes. A client/end user should be connecting to the redirect server. |
NIOS-X Servers | ntp.ubuntu.com (optional) pool.ntp.org (optional) | N/A | UDP | 123 | For NTP server synchronization. Needed only when ESXi time sync is disabled. This is optional. |
...
Source | Destinations | Destination IPs (if applicable) | Protocol | Destination | Description |
|---|---|---|---|---|---|
BloxOne Infoblox admins | US Region
EU Region
| N/A | TCP (TLS) | 443 |
|
Port Usage for
...
Infoblox Services
The following table lists the ports that must be available in your firewall for BloxOne Infoblox services to function properly.
...
Services | Protocol | Destination Port | Description |
|---|---|---|---|
All BloxOne Infoblox services | TCP | 443 |
|
DNS Forwarding Proxy | TCP UDP | 53 | DNS forwarding proxy uses 52.119.40.100 as the default resolver. However, you can use your own local resolver to resolve the destination domains. |
DHCP server | UDP | 68 | N/A |
BloxOne Infoblox DNS | TCP | 443 | For BloxOne Universal DDI authoritative DNS cloud services.
|
Sending peer of the DHCP HA (High Availability) | TCP | 647 | This is an incoming port for the HA (High Availability) feature. The receiving peer must be able to receive traffic on the port, and the sending peer must be able to send traffic to the port, generally from other random ports. |
Sending peer of the DHCP cluster | TCP | 647 or 847 | For DHCP cluster load balancing. The receiving peer must be able to receive traffic on the port, and the sending peer must be able to send traffic to the port, generally from other random ports. |
Data Connector | TCP | 22 | Open this port if you want to send data using SCP from the Infoblox NIOS appliance (if configured) to Data Connector. The NIOS UI provides a mechanism to filter the domains it sends to Data Connector. Since NIOS is sending cache logs, when configuring NIOS for use with Data Connector, make sure to configure Data Connector to exclude internal corporate and authoritative domains (*.<corp>/Authorititative). By excluding corporate and authoritative domains, internal traffic logs will not be added. Required for incoming SCP data transfer from NIOS to Data Connector when deployed as a container. When you deploy Data Connector as a container, ensure that there are no SSH processes listening on port 22. You must terminate these SSH processes for Data Connector to collect data from NIOS. If you deploy Data Connector as a container, ensure that there are no SSH processes listening on port 22. You must terminate these SSH processes for Data Connector to collect data from NIOS. |
Data Connector | TCP | 514 | Open this port if you want to send syslog and secure syslog for RPZ from the Infoblox NIOS appliance (if configured) to Data Connector. Note: Port 514 is an insecure port. The NIOS UI provides a mechanism to filter the domains it sends to Data Connector. Since NIOS is sending cache logs, when configuring NIOS for use with Data Connector, make sure to configure Data Connector to exclude internal corporate and authoritative domains (*.<corp>/Authoritative). By excluding corporate and authoritative domains, internal traffic logs will not be added. Required for Data Connector secure syslog for RPZ hits data. If you deploy Data Connector as a container, ensure that this port is not used by other processes. If you deploy Data Connector as a container, ensure that this port is not used by other processes for Data Connector to collect data from NIOS. |
Data Connector | TCP | 6514 | Open this port if you want to send syslog and secure syslog for RPZ from the Infoblox NIOS appliance (if configured) to Data Connector. The NIOS UI provides a mechanism to filter the domains it sends to Data Connector. Since NIOS is sending cache logs, when configuring NIOS for use with Data Connector, make sure to configure Data Connector to exclude internal corporate and authoritative domains (*.<corp>/Authoritative). By excluding corporate and authoritative domains, internal traffic logs will not be added. Used for transferring syslog data from NIOS to Data container. Port 6514 is a default secure port. If you deploy Data Connector as a container, ensure that this port is not used by other processes. If you deploy Data Connector as a container, ensure that this port is not used by other processes for Data Connector to collect data from NIOS. |
...
For additional information on requirements for the BloxOne Infoblox connectivity service, see the following:
...