Differences

This shows you the differences between two versions of the page.

--- infoblox_uddi:nios_x_servers [2026/02/18 16:23] – [NIOS-X Server Objects] bstafford
+++ infoblox_uddi:nios_x_servers [2026/03/07 02:47] (current) – [Repairing NIOS-X Server] bstafford
@@ Line 36: / Line 36: @@
   * DNS Zones
     * DNS Authoritative Zones
-    * DNS Delegation Zones
+    * DNS Delegation Zones (Feb 2026, currently counted as NS record)
     * DNS Forward Zones
     * DNS Secondary Zones
+    * DNS RPZ Zones (Feb 2026, currently counted as Auth Zone)
   * DNS Records
     * A Records
@@ Line 62: / Line 63: @@
   * Fixed Addresses
   * Reservations
+      * Note: While the network IP address and broadcast IP address of every subnet in the Infoblox Portal counts towards Management Tokens, they are not counted towards server object count on NIOS-X.
   * Fingerprints
+  - DHCP Exclusion Ranges
+    - Note: DHCP Exclusion Ranges are not counted as server objects directly
+    - Note: If a DHCP Exclusion Range consists of 20 or fewer IP addresses, then each IP address is represented in the DHCP config as a reservation with a multicast MAC address (03-xx-xx-xx-xx-xx). These reservations are added to the server object count but do NOT get counted for Management Tokens. Only the single Exclusion Range gets counted for Management Tokens.
+    - Note: If the DHCP Exclusion Range consists of 21 or more IP addresses, then the parent range is split into two ranges either side of the Exclusion Range. Both ranges will be added to the server object count but only the single range seen in the Infoblox Portal will be counted for Management Tokens. Only the single Exclusion Range gets counted for Management Tokens.
+A DNS Zone or DNS Record is counted towards the server object count of a NIOS-X server if, and only if, that NIOS-X server is authoritative for that Zone/Record.
+While a secondary zone counts as a “server object”, the contents (records) of that zone do not count towards “server object” of NIOS-X regardless of whether the Infoblox Portal enables visibility of the secondary zone data. Visibility of secondary zone data will impact Management Token count.
+A subnet/range will only be on a NIOS-X server if that NIOS-X server is assigned as the Member server or part of the HA pair assigned to that subnet/range.
+A fixed address, reservation, or DHCP lease will only be on a NIOS-X server if they are in a subnet and/or DHCP range that the NIOS-X server has been assigned to directly or as part of a HA pair.
+For DHCP active-active mode, active-passive mode, advanced active-passive mode, and hub-spoke mode, a lease on the HA pair is added to the server object count on both NIOS-X members in the HA pair. The lease will be considered a single lease when counted as an Active IP address for Management tokens.
+Example: 5 “spoke” sites have 100 leases which means they have 100 lease server objects each. The Hub NIOS-X server will have 500 lease server objects.
 ===== Dig Testing =====
 The following should always work
@@ Line 70: / Line 89: @@
 The following will only work when querying from a public IP that is in an External Network definition in your Infoblox Threat Defense Tenant.
 <code>dig @52.119.41.100 +short A www.google.com</code>
+===== NIOS-X API Monitor ======
+You can monitor NIOS-X servers via API. SNMP is not supported. Docs [[infoblox:api#nios-x_host_monitoring|here]].
+===== NIOS-X Server Size =====
+Changing the size of a NIOS-X server by editing it has no impact on the operations of that NIOS-X server (i.e. no config changes, no service reboots, etc)
 ===== NIOS-X Server Deployment =====
 ==== Best Practice ====
@@ Line 178: / Line 202: @@
 Run PowerShell as administrator and convert the downloaded VHD file from dynmaic-size to fixed-size with:
 <code>Convert-VHD -Path C:\Users\name\Downloads\b1dynamic.vhd -DestinationPath C:\Users\Downloads\b1fixed.vhd -VHDType Fixed</code>
+===== NIOS-X OS =====
+March 2026 saw the release of NIOS-X 4.0.0 image. This runs Ubuntu 24.04. Older 3.x images run Ubuntu 20.04.3 (with extended security support).
+Servers running 3.x cannot upgrade to 4.0. The VM must be redeployed. Hardware must be flashed from USB. B1-105 does not support new image.
 ===== Repairing NIOS-X Server =====
 The B1-105 appliance can be rebuilt using the ISO image that is available for the Dell VEP servers.