...
NIOS-X Port Usage for Server Connectivity
Admin User Connectivity Requirements
Port Usage for Infoblox Services
Port Usage for Bare-Metal NIOS-X Servers
Connectivity Rules for DNS Forwarding Proxy
Forwarding DNS Traffic to Infoblox Platform
Infoblox Geo-Based Anycast IPs for POPs
Local DNS Request Processing Optimization
NIOS-X Port Usage for Server Connectivity
For NIOS-X server connectivity to function properly, ensure that the following are in place:
All destination domains, IPs, and ports listed in the following table must be available in your firewall.
Do not enable SSL inspection in your firewall for any of the destination domains and IPs.
...
Source
...
Destinations
...
Destination IPs
...
Protocol
...
Destination
Port
...
Description
...
Universal DDI
...
US Region
dns.bloxone.infoblox.com
http://csp.infoblox.com
cp.noa.infoblox.com
grpc.csp.infoblox.com
app.noa.infoblox.com
EU Region
dns.bloxone.eu.infoblox.com
http://csp.eu.infoblox.com
cp.noa.eu.infoblox.com
grpc.csp.eu.infoblox.com
app.noa.eu.infoblox.com
US Region
dns.bloxone.infoblox.com
18.235.106.26
54.224.108.101
34.194.149.196
http://csp.infoblox.com
18.235.149.1
18.209.243.220
18.233.189.178
cp.noa.infoblox.com
3.209.116.255
3.210.226.54
3.212.42.44
grpc.csp.infoblox.com
3.209.116.255
3.210.226.54
3.212.42.44
app.noa.infoblox.com
3.213.214.20
3.214.194.152
3.214.29.106
EU Region
dns.bloxone.eu.infoblox.com
18.153.44.29
18.197.230.152
18.184.150.241
http://csp.eu.infoblox.com
3.70.109.229
3.73.182.10
3.66.44.28
cp.noa.eu.infoblox.com
grpc.csp.eu.infoblox.com
3.124.178.19
3.64.74.162
3.73.242.251
app.noa.eu.infoblox.com
3.71.171.160
3.123.100.200
18.193.177.184
...
TCP
...
443
...
Allow these IP addresses on the firewall for the NIOS-X servers to connect to the Infoblox Portal, and to ensure 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)
ope.infobloxtd.com (and all subdomains) Note that this destination domain is required only if you plan to use the “Local On-Prem resolution” feature.
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 Universal DDI service destination (dns.bloxone.infoblox.com:443) is bypassed on the proxy.
...
US and EU Regions
Anycast IPs (IPv4 and IPv6)
52.119.40.100 (default resolver)
52.119.41.100
52.119.41.120
103.80.5.100
103.80.6.100
103.80.6.120
2620:129:6000::100
2400:4840::100
For geo-specific IP addresses, refer to the Infoblox geo-based Anycast IPs for POPs table in Forwarding DNS Traffic to Infoblox Platform.
...
TCP
...
443
53
...
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
http://csp.infoblox.com
cp.noa.infoblox.com
grpc.csp.infoblox.com
app.noa.infoblox.com
tide.infoblox.com
threatdefense.infoblox.com (and all subdomains)
EU Region
http://csp.eu.infoblox.com
...
cp.noa.eu.infoblox.com
...
grpc.csp.eu.infoblox.com
...
app.noa.eu.infoblox.com
...
US Region
A complete list of the US region IP addresses is available in a JSON file by clicking this link.
EU Region
A complete list of the EU region IP addresses is available in a JSON file by clicking this link.
If the server type is NIOS, do the following:
For NIOS versions less than or equal to 8.6.4, or for NIOS versions less than or equal to 9.0.2: Allow US domains grpc.csp.infoblox.com (3.210.226.54, 3.209.116.255, 3.212.42.44) and
http://csp.infoblox.com
(18.233.189.178, 18.235.149.1, 18.209.243.220), along with all EU region destination IPs.
For NIOS versions greater than or equal to 8.6.5, or for NIOS versions greater than or equal to 9.0.3, do the following:
For NIOS DNS resolver: Allow external domain lookup and all EU region destination IPs.
For NIOS running behind HTTPS Proxy and if external domain lookup is denied: Allow domain
provision.ib-hub.na.csp.infoblox.comand this IP address44.218.80.45, along with all EU region destination IPs.
HTTP proxy configured on NIOS-X server
When a HTTP proxy is configured on NIOS-X server, Data Connector is able to pull the log data from Infoblox cloud source through configured proxy. However, do note that as of now the logs sent from data connector to the configured destination will still bypass the proxy.
...
TCP
...
443
...
All listed IPs require TCP 443 port be open when being used.
...
End Client
...
N/A
...
Redirect IPs:
For IPv4:
3.215.231.251
3.216.243.225
35.168.95.233
54.173.31.46
3.220.140.235
For IPv6:
2600:1f18:1043:dc00:8083:68e:ef0f:46de
2600:1f18:1043:dc02:ed26:448b:247:90c9
2600:1f18:1043:dc00:a339:63ac:4c02:9531
2600:1f18:1043:dc00:5ee5:908d:8892:f214
2600:1f18:1043:dc02:be4:9bb:7833:d9d4
...
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)
http://pool.ntp.org
(optional)
...
N/A
...
UDP
...
123
...
For NTP server synchronization.
Needed only when ESXi time sync is disabled. This is optional.
Admin User Connectivity Requirements
Source | Destinations | Destination IPs (if applicable) | Protocol | Destination | Description |
|---|---|---|---|---|---|
Infoblox admins | US Region
http://auth.infoblox.com
http://cdnjs.cloudflare.com
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 Infoblox services to function properly.
All ports listed below are outbound only, except for transferring logs from NIOS to Data Connector, which requires inbound communication.
Services | Protocol | Destination Port | Description |
|---|---|---|---|
All 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 |
Infoblox DNS | TCP | 443 | For 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. |
| Info |
|---|
A complete list of the used IP addresses is available in a JSON file by clicking this link. All listed IPs require TCP 443 port be open when being used. |
For additional information on requirements for the Infoblox connectivity service, see the following:
Port Usage for Bare-Metal NIOS-X ServersDownloading Endpoint
NIOS-X Server Connectivity and Service Requirements
| Include Page | ||||
|---|---|---|---|---|
|
Port Usage for Bare-Metal NIOS-X Servers
When deploying a bare-metal NIOS-X server, you must open applicable ports on the server to ensure that all services are functioning properly.
...
IP Protocol | Port | Services using this port | Description |
|---|---|---|---|
TCP | 22 |
| 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. |
TCP | 53 |
| Ensure that there are no other processes using port 53 on the server system on which your server will be deployed. For example, some Ubuntu systems running local DNS cache (system-resolved) might occupy port 53, and your server might not function properly in this case. |
TCP | 514 |
| 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. |
TCP | 2222 |
| Used by an internal service for remote monitoring. |
TCP | 6514 |
| 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. |
TCP | 8125 |
| This is an internal port used for communications between containers. If you deploy Data Connector as a container, ensure that this port is not used by other processes. |
TCP | 8126 |
| This is an internal port used for communications between containers. If you deploy Data Connector as a container, ensure that this port is not used by other processes. |
TCP | 50514 |
| This is an internal port used for communications between containers. If you deploy Data Connector as a container, ensure that this port is not used by other processes. |
Connectivity Rules for DNS Forwarding Proxy
The DFP makes its connection with Infoblox Platform-based on the following rules and conditions:
...
Forwarding DNS Traffic to Infoblox Platform
To access Infoblox Platform DNS service, you must forward your DNS traffic (except for internal domain resolution) to the 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.
...
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.
Infoblox Geo-based Anycast IPs for POPs | |||
|---|---|---|---|
Location | IPv4 Address | Secondary IPv4 Address | Server |
California (USA) | 52.119.41.51 | 103.80.6.51 | us-west-1-geo.threatdefense.infoblox.com |
Virginia (USA) | 52.119.41.52 | 103.80.6.52 | us-east-1-geo.threatdefense.infoblox.com |
London (England) | 52.119.41.53 | 103.80.6.53 | eu-west-2-geo.threatdefense.infoblox.com |
Frankfurt (Germany) | 52.119.41.54 | 103.80.6.54 | eu-central-1-geo.threatdefense.infoblox.com |
Mumbai (India) | 52.119.41.55 | 103.80.6.55 | ap-south-1-geo.threatdefense.infoblox.com |
Tokyo (Japan) | 52.119.41.56 | 103.80.6.56 | ap-northeast-1-geo.threatdefense.infoblox.com |
Singapore | 52.119.41.57 | 103.80.6.57 | ap-southeast-1-geo.threatdefense.infoblox.com |
Toronto (Canada) | 52.119.41.58 | 103.80.6.58 | ca-central-1-geo.threatdefense.infoblox.com |
Sydney (Australia) | 52.119.41.59 | 103.80.6.59 | ap-southeast-2-geo.threatdefense.infoblox.com |
São Paulo (Brazil) | 52.119.41.60 | 103.80.6.60 | sa-east-1-geo.threatdefense.infoblox.com |
Bahrain | 52.119.41.61 | 103.80.6.61 | me-south-1-geo.threatdefense.infoblox.com |
Johannesburg (South Africa) | 52.119.41.62 | 103.80.6.62 | af-south-1-geo.threatdefense.infoblox.com |
Ohio (USA) | 52.119.41.63 | 103.80.6.63 | us-east-2-geo.threatdefense.infoblox.com |
| Note |
|---|
Warning |
Local DNS Request Processing Optimization
To reduce the number of noise requests forwarded to the cloud and to avoid misconfiguration, DFP and 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.
DFP will forward all private requests to a local DNS server by default when a local DNS server is provisioned on the DFP.
Downloading Endpoint
| Include Page | ||||
|---|---|---|---|---|
|