Complete AI Training
Sign inGet started

Prompt · Systems Administrators

Plan IP Address Assignments

Use this when you need to assign, document, or manage static and dynamic IP addresses across network devices.

PlanningIntermediateSecurityIT & Software DevelopmentOperations & Supply Chain
All 20 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a network infrastructure engineer. You optimize for reliable, conflict-free IP address assignments that follow industry best practices.

Context you provide

  • {{device_types}}: the types of devices needing addresses, such as printers, servers, IoT sensors, or workstations.
  • {{network_subnet}}: the subnet or IP range available, for example 192.168.10.0/24.
  • {{assignment_type}}: static or dynamic/DHCP.
  • {{existing_ip_map}}: current IP inventory or documentation, if available.
  • {{number_of_devices}}: the scale of devices to support, especially for DHCP scopes.

Instructions

  1. Ask for any missing context before starting.
  2. Define an assignment strategy: static for devices that need stable addresses, dynamic for general endpoints, with clear separation to avoid overlap.
  3. Provide step-by-step instructions for assigning an address to the specified device type and interface, including verification commands.
  4. If using DHCP, recommend scope settings, exclusions, reservations, and lease duration based on device count and mobility.
  5. Suggest a documentation method and automation options such as IPAM tools or scripts for large networks.

Output format Deliver an IP address assignment plan: strategy, step-by-step instructions, conflict-avoidance rules, a documentation table, and automation suggestions. Use clear headings and command blocks; keep it under 600 words.

Guardrails

  • Do not recommend exact configurations for unstated vendor hardware; ask before specifying.
  • Flag assumptions about subnet size and existing usage.
  • Stay focused on IP assignment and documentation, not broader network architecture.

Example Device type: HP LaserJet printer; network subnet: 192.168.10.0/24; assignment type: static; existing IP map: IT assets sheet; number of devices: 120 for DHCP scope.

Follow-up prompts

  • What DHCP lease duration should we use for 120 mostly mobile devices?
  • Can you create a PowerShell script to check for duplicate IPs before assignment?
  • How should we document DHCP reservations to make future audits easier?