IP Addresses

The IP Addresses section allows administrators to manage and allocate public and private IPs for use across virtual machines, NAT configurations, and web services. This tool provides control over IP assignment, NAT bindings, server association, and exportable audit data.

IP Address List View

This list shows all IP addresses currently defined in the system. Each entry is tied to a specific server, user, or purpose.

Interface elements:

• Add IP Address – Opens a form to add a new IP or range of IPs.
• Edit selected – Allows bulk editing of selected IP entries.
• Delete selected – Deletes selected entries from the list.
• Pool dropdown – Filters results by predefined pool types such as:
  • General
  • Web Sites
  • VPS External Network IP
  • VPS Management Network IP
• Download Report – Exports the IP address list in .xlsx format.

Columns displayed:

• IP Address – Individual or range of assigned IP addresses (e.g., 192.168.10.10).
• NAT Address – Optionally mapped NAT target (e.g., 10.0.0.10).
• Server – Associated server or gateway (e.g., vm-hyperv01).
• User – If assigned to a specific user (e.g., admin@customer.org).
• Space – Linked storage or service space (e.g., web-tier01).
• Item – The resource using the IP (e.g., VM-SQL01).
• Location – Internal notes or physical location (e.g., Rack C3 / DC-2).
• Comments – Custom notes such as “Reserved for client onboarding” or “Staging environment pool.”

Adding an IP Address

To add a new IP address or a range:

1. Pool – Select from one of the predefined pool types.
2. Server – Assign the IP to a server or leave as Not Assigned.
3. IP Address – to – Enter the start and end IP to define a range (e.g., 192.168.20.50 to 192.168.20.60) or a single IP.
4. NAT Address – If applicable, enter the NAT IP (e.g., 10.0.2.25).
5. Comments – Add notes such as:
   • “Assigned for beta test VMs”
   • “Linked to corporate VPN gateway”
   • “Used in isolated lab environment”

Actions:

• Add – Commits the IP entry to the system.
• Cancel – Exits the form without saving.

Best Practices

• Use clearly documented comments to track the purpose of IPs (e.g., “Allocated to ACME Corp VPN” or “Available for DevOps team”).
• Maintain separate pools for external and internal IPs to simplify firewall and NAT configuration.
• Use NAT mappings to securely expose internal services like RDP or SFTP from external sources.
• Download XLSX reports regularly for auditing and cleanup of unused IP addresses.
• Pre-plan IP ranges for tenant separation in multi-tenant environments to avoid overlaps.