VDS Control Panel Features: What a Good One Must Do

A good VDS control panel lets you manage the whole server lifecycle yourself, without opening a support ticket. At a minimum it should offer a browser-based console, one-click Windows and Linux installs, custom ISO upload, PTR (reverse DNS) editing, backup restore, and instant RAM, disk, and IP changes.

If a panel lacks any of these, a routine task such as a broken network config, a reinstall, or a mail server PTR fix turns into a wait. This guide explains what each feature should do, how to verify it, and which commands you need on the guest side. The panel only changes the virtual hardware. The operating system still has to be told about it.

Quick checklist

Browser console: your safety net

The console should show what a physical monitor would show. That means BIOS/UEFI, the bootloader, and the login screen, all reachable even when the guest has no working network. It is the tool you use when a firewall rule locks you out, when /etc/fstab has a typo and the system drops to emergency mode, or when a netplan change leaves the interface down.

What to test on any panel:

• Can you send Ctrl+Alt+Del and paste text?
• Can you power cycle, reset, and shut down gracefully from the same page?
• Can you mount and unmount an ISO from the console view?
• Does the session work from a modern browser without a legacy plugin?

On Linux, a typical console recovery after a bad firewall change is:

# From the browser console, logged in as root
sudo nft flush ruleset      # or: sudo iptables -F
sudo systemctl restart networking   # or: sudo netplan apply

Fix the rules, then re-enable the firewall. Never leave it flushed.

One-click Windows and Linux installs

Template-based installs should finish in minutes. Look at what happens after deployment. A good panel lets you choose the OS version and either set the initial password or inject an SSH key. It should also show the install status.

After a fresh install, do the following:

1. Change the initial password or disable password SSH login.
2. Run a full update (apt update && apt full-upgrade or dnf upgrade; Windows Update on Windows).
3. Confirm the hostname, time zone, and time sync.
4. Restrict RDP and SSH to known source addresses.

A minimal SSH hardening snippet:

# /etc/ssh/sshd_config.d/10-hardening.conf
PermitRootLogin prohibit-password
PasswordAuthentication no

Test the key login in a second session before you reload sshd.

Uploading your own ISO

The template list never covers everything. You may need FreeBSD, a router or firewall distribution, a rescue image, or a hardened golden image of your own. A panel should let you upload an ISO, mount it as virtual media, and choose to boot from it.

Practical tips:

• Verify the checksum before and after upload so you know the image is intact:

bash sha256sum debian-12-netinst.iso

• Match firmware. If the VM boots UEFI, the ISO must support UEFI. Secure Boot can block unsigned images.
• Use paravirtual drivers on VMware-based platforms. On a vSphere-based VDS, Windows installers usually will not see a paravirtual SCSI disk or a VMXNET3 NIC until you load drivers. Linux kernels include them. Check which controller type your VM uses.
• Detach the ISO after install. Otherwise the VM may boot into the installer again after a reboot.

Setting PTR (reverse DNS)

A PTR record maps an IP address back to a hostname. Mail servers check it. Many receivers reject or penalize mail from an IP with no PTR or a generic one. The panel should let you set a PTR for each IP assigned to your VDS.

Verify it with dig:

dig -x 192.0.2.10 +short
# mail.example.com.

dig +short A mail.example.com
# 192.0.2.10

The two lookups should agree. This is called forward-confirmed reverse DNS. Also make sure the SMTP banner and HELO name match the same hostname. If you also run mail on IPv6, set the PTR for that address too, for example under 2001:db8::/32 documentation space in a lab. Our guide to running a mail server on a VDS covers the rest of the deliverability stack: SPF, DKIM, and DMARC.

Common mistake: setting the PTR before the A record exists. Create the forward record first, wait for DNS propagation, and then change the PTR.

Restoring from a Veeam backup

A backup is useful only if you can restore it. When a provider uses Veeam, the panel should let you see available restore points and start a restore without a ticket. The restore options you care about are:

• Full VM restore: roll the whole server back to a previous state.
• Restore to a new VM: bring the old state up next to the current one for comparison. Watch for IP conflicts. Keep the copy off the network until you have changed its addresses.
• File-level restore: pull one config file or database dump instead of rolling back everything.

Habits that save you:

1. Take or confirm a fresh restore point before kernel upgrades, major application upgrades, and firewall rewrites.
2. Test a restore on a non-critical VM at least once, so you know how long it takes.
3. For databases, also keep logical dumps (pg_dump, mysqldump). A crash-consistent image of a busy database may need recovery after it is restored.
4. Check retention. A restore point from last week does not help if the problem began a month ago.

Features and retention vary by plan, so check the exact backup options on the plan details.

Instant RAM, disk, and IP changes

Scaling should not need a rebuild. Three cases come up most often.

Adding disk

After you enlarge the virtual disk in the panel, the guest still sees the old partition size. On Linux with ext4:

echo 1 | sudo tee /sys/class/block/sda/device/rescan
sudo growpart /dev/sda 1
sudo resize2fs /dev/sda1
# For XFS, use: sudo xfs_growfs /

If you use LVM, run pvresize, lvextend -r, and then check with df -h. On Windows, open Disk Management and choose Extend Volume, or use PowerShell:

$max = (Get-PartitionSupportedSize -DriveLetter C).SizeMax
Resize-Partition -DriveLetter C -Size $max

Take a restore point before you touch partitions.

Adding RAM

Hot-added memory may show up as offline blocks on Linux. Check it:

free -h
grep -c offline /sys/devices/system/memory/memory*/state

To bring new memory online automatically, add a udev rule:

# /etc/udev/rules.d/99-memory-hotplug.rules
SUBSYSTEM=="memory", ACTION=="add", ATTR{state}=="offline", ATTR{state}="online"

Whether RAM can be added while the VM runs depends on the guest OS and VM settings. If it cannot, a quick reboot is still much faster than a migration.

Adding IPs

An extra IP from the panel is only a routing allocation. You must configure it in the guest. With netplan on Ubuntu:

# /etc/netplan/50-cloud-init.yaml
network:
  version: 2
  ethernets:
    ens192:
      addresses:
        - 192.0.2.10/24
        - 192.0.2.11/24
      routes:
        - to: default
          via: 192.0.2.1

Apply it with sudo netplan try. This command reverts the change automatically if you lose connectivity. On Windows, add the address under the adapter's Advanced TCP/IP settings. Use the gateway and prefix length shown in the panel, not guesses.

Extras for networks with their own ASN

If you run your own ASN and prefixes, the panel is only half the story. You need BGP session support on the VDS itself. Nixcon operates AS40368, and our BGP-enabled VDS lets you announce your own ASN and IP block from a BGP session on the server. Ownership is validated against RPKI ROAs and RIR/IRR records. Options include announcements with or without DDoS protection, and a full routing table. Check the public looking glass to confirm how your prefix looks from Frankfurt, the US, and Izmir, Turkey.

Common mistakes and fixes

• Disk enlarged but df -h is unchanged. You skipped the partition and filesystem grow steps above.
• Extra IP added but unreachable. The address is not configured in the guest, or the prefix length or gateway is wrong. Use the console to fix it.
• Custom ISO keeps booting. Eject it in the panel and fix the boot order.
• Mail rejected despite correct SPF. The PTR and HELO do not match, or there is no forward record.
• Restore brings up an IP conflict. You restored to a new VM and left it on the production network. Isolate it first.
• Locked out after enabling a firewall. Use the console, not a support ticket. This is why the console matters most.

What to ask before you choose

Before you pay for a VDS, ask the provider these questions:

1. Can I use the console when the guest network is down?
2. Can I mount my own ISO and set boot order?
3. Can I set PTR for every IP myself?
4. Which restore options exist, and how many restore points are kept?
5. Which resource changes are live, and which need a reboot?
6. Is DDoS protection available if I host public services? See our DDoS protection and firewall options.

A panel that answers yes to these saves hours every month, and it is easy to confirm with a short test before you commit.