Mohammad@soultion.in

Infrastructure purchasing · Dedicated · GPU · Cloud

MMustaq

Useful tools · network setup

Static IP configuration generator

Got an IP allocation email from your hosting provider and not sure what to do with it? Copy the values into this guide, choose the operating system, and get a clear, human-readable setup path. Linux users can also download a ready-to-review setup script.

Start with your provider’s network email

Look for an IP address, subnet / prefix, gateway, and DNS servers. This tool runs entirely in your browser—nothing you enter is sent anywhere.

What the network details mean

These are the usual fields in an IP allocation email. The provider may use slightly different names, but the purpose is the same.

IP addressThe unique address assigned to your computer or server. Do not invent one—use the exact address your provider allocated.
Prefix or subnet maskDefines which addresses are on the local network. Providers may write /24 instead of 255.255.255.0; both describe the same thing.
GatewayYour route off the local network. It is commonly the first or last usable address, but always use the provider’s stated value.
DNS serversTranslate names such as example.com into IP addresses. Provider DNS is normally best when it is supplied.
IPv6 addressA second, longer address. It is optional here because many allocations are IPv4-only. Enter it only when the provider assigned one.
Linux interfaceThe actual network port name on the OS—not a hostname. Check it with ip link before running a generated script.

Quick subnet-mask reference

If the provider gives a subnet mask rather than a slash prefix, use this common conversion.

PrefixSubnet maskTypical usable IPs
/24255.255.255.0254
/29255.255.255.2486
/30255.255.255.2522
/32255.255.255.255One routed address

Common questions

Enter the single IP address allocated to this machine, then enter the prefix length separately. A range only tells you the network block; the provider should identify which address and gateway belong to your server.

Choose Ubuntu Server if the machine uses Netplan (common on modern Ubuntu). Choose NetworkManager for RHEL, AlmaLinux, Rocky, and Fedora. If you are unsure, run command -v netplan and command -v nmcli first.

DNS is optional. Use the DNS servers supplied by your provider where possible; if none were supplied, ask support which resolvers they recommend before adding public DNS.

You can, but a network change may terminate the session. Keep your provider’s web console or KVM open first, verify the interface name, and test the generated script before applying it.

Network tools

Plan addresses and prepare email networking

Use these before you assign an address, configure a subnet, or put a mail server on a new IP.

IPv4 subnet / CIDR calculator

Turn an IPv4 address and prefix into its network, broadcast address, mask, and usable-host count.

IPv6 subnet planner

See how many smaller subnets a delegated IPv6 block can provide. This is useful for VPS, VLAN, or client planning.

Email IP & DNS checklist

Get a clean launch checklist for a self-hosted mail or transactional-email server.

Server planning tools

Size the server and budget before you order

These estimates are planning starting points. Confirm final hardware, port terms, and pricing with the provider.

Server RAM estimator

Get a sensible RAM starting point for a common workload.

RAID / storage calculator

Compare usable storage and disk-failure tolerance before selecting a server configuration.

Bandwidth estimator

Estimate monthly transfer from visitors, page weight, and a traffic multiplier for assets and bots.

Download / migration time

Estimate how long a backup restore or server migration takes at a realistic share of the port speed.

Server cost calculator

See the first-year and ongoing cost including setup fees and monthly add-ons.

Server setup tools

Start a server on the right footing

Use the checklist after provisioning and use the matcher if you are still deciding which class of hardware to order.

Linux server setup checklist

Create a focused first-day checklist based on the server’s role.

CPU / GPU workload matcher

Describe the main pressure point and get a practical configuration direction.