...
| Warning | ||
|---|---|---|
| ||
The minimum system requirements specified for hosts must be dedicated to the host you plan to deploy. They cannot be shared with or used for other non-Infoblox applications. Doing so will negatively affect the performance of your BloxOne services. For information about the minimum system requirements and port usage, see the following: |
To ensure a successful deployment of hosts, consider the following best practices:
...
- When setting up DNS forwarding proxies as hosts for failover purposes, Infoblox recommends that you deploy two DNS forwarding proxies using one as the primary proxy and the other as the secondary.
- If you have configured any name servers through the DHCP options or hosts, ensure that you point them to the DNS forwarding proxies.
- If you change the IP address or make any configuration changes on the host outside of the Cloud Services Portal, you must restart the system for the change to take effect. If the change is made within the BloxOne Cloud infrastructure, no restart is required.
- For DNS to function properly in OVA deployments on ESXi servers, ensure that you enable the Synchronize guest time with host option during the deployment and that your ESXi host is synchronized with the NTP server. If you do not select the Synchronize guest time with host option (or if this option is disabled), the host synchronizes with the Ubuntu NTP servers: ntp.ubuntu.com and ubuntu.pool.ntp.org. When you disable this option, ensure that you open the UDP 123 port for time synchronization with the Ubuntu NTP servers. For more information, see Synchronizing Time with NTP Servers.
When you enable hosts to BloxOne Threat Defense Cloud on a NIOS appliance, the QPS (query per second) throughput might vary, depending on your appliance models and the cache hit ratios. You might see a bigger performance impact when the cache hit ratio is lower. In general, NIOS can forward at least 3,500 QPS to BloxOne Threat Defense Cloud. For standalone installations, the QPS may vary depending on the hardware used and the cache hit. However, the number of queries per second should fall in the range of 3,500 QPS using an OVA with 512 MB memory and 1 CPU.
- BloxOne has configured
52.119.40.100as the default DNS resolver for all hosts, so you are not required to configure a local DNS resolver. However, if you do not want to use52.119.40.100as the default DNS resolver and you do not want Docker to resolve DNS queries using8.8.8.8or8.8.4.4, you must configure at least one non-local DNS resolver. If you use only local DNS resolvers, Docker will resolve DNS queries using8.8.8.8or8.8.4.4. Note that Infoblox does not recommend using the loopback address (127.0.0.1) when configuring a non-local DNS resolver.
...
- For any host using the BloxOne DDI capabilities, the interface should be reachable through LAN/WAN for queries from external clients to be resolved.
- When setting up DNS forwarding proxies as hosts for failover purposes, Infoblox recommends that you deploy two DNS forwarding proxies using one as the primary proxy and the other as the secondary.
- If you have configured any name servers through the DHCP options or hosts, ensure that you point them to the DNS forwarding proxies.
- If you change the IP address or make any configuration changes on the host outside of the Cloud Services Portal, you must restart the system for the change to take effect. If the change is made within the BloxOne Cloud infrastructure, no restart is required.
- For DNS to function properly in OVA deployments on ESXi servers, ensure that you enable the Synchronize guest time with host option during the deployment and that your ESXi host is synchronized with the NTP server. If you do not select the Synchronize guest time with host option (or if this option is disabled), the host synchronizes with the Ubuntu NTP servers: ntp.ubuntu.com and ubuntu.pool.ntp.org. When you disable this option, ensure that you open the UDP 123 port for time synchronization with the Ubuntu NTP servers. For more information, see Synchronizing Time with NTP Servers.
- BloxOne has configured
52.119.40.100as the default DNS resolver for all hosts, so you are not required to configure a local DNS resolver. However, if you do not want to use52.119.40.100as the default DNS resolver and you do not want Docker to resolve DNS queries using8.8.8.8or8.8.4.4, you must configure at least one non-local DNS resolver. If you use only local DNS resolvers, Docker will resolve DNS queries using8.8.8.8or8.8.4.4. Note that Infoblox does not recommend using the loopback address (127.0.0.1) when configuring a non-local DNS resolver.
...