What Is a Hostname?
Short answerA hostname is a label for a machine on a network — for example vps01 or app.dallas.example.com. At VPSGrid checkout you set a Hostname for your VPS; that is not the same as registering a public website domain. Visitors reach your site via DNS A records to your primary IP.
Overview
Hostname confusion causes many first-ticket support questions: customers expect the hostname field to publish their website automatically. It does not. This article separates hostname, domain, and FQDN so you configure orders and DNS correctly. See also How to Point a Domain to a VPS.
Hostname vs domain vs FQDN
| Term | What it is | Example |
|---|---|---|
| Hostname | Name identifying one computer/server | web1, vps-prod-01 |
| Domain | Registered DNS zone you control | example.com |
| FQDN (fully qualified domain name) | Hostname + domain chain | web1.example.com |
Your VPS can have an internal hostname like vps01 while your website lives at www.example.com — as long as DNS points the domain to your VPS IP and the web server is configured for that name.
Why VPSGrid asks for a hostname at order
During checkout, the Hostname field labels your service for:
- Provisioning and service records in the client area
- Default system identity inside the guest OS (Linux/Windows may adopt or mirror it)
- Reverse DNS (PTR) defaults tied to your primary IP — What Is a Public IPv4 Address?
- Support tickets and welcome email clarity
It does not register a domain or create public DNS records for you.
Valid hostname formats
Use simple, DNS-safe names:
- Letters (
a–z), numbers (0–9), and hyphens (-) - Start and end with a letter or number (avoid leading/trailing hyphens)
- Keep it readable —
vps-dallas-app1beats random strings for later admin work - Avoid spaces, underscores in the order field (Linux allows underscores in some contexts; keep checkout names conservative)
Examples that work well:
vps01prod-web-01client-acme-vps
A hostname can be a single label (vps01) or an FQDN-style value if you already control the domain and want rDNS alignment — confirm PTR policy with support if needed.
Hostname inside the operating system
After provisioning, the guest OS has its own hostname setting:
- Linux — shown in shell prompts; change with
hostnamectl— How to Change a Linux Hostname - Windows — Computer name in System settings
Changing the OS hostname does not automatically update billing labels or public DNS. Treat order-time hostname, OS hostname, and website domain as three related but separate settings.
Common mistakes
- Entering
www.mysite.comand expecting the site to work — you still need DNS A records and a web server vhost/binding - Confusing hostname with primary IP — SSH/RDP use the IP (or DNS once configured), not the internal hostname alone from outside
- SSL certificate errors — certificates validate domain names visitors type, not arbitrary internal hostnames
Frequently Asked Questions
Can I change my hostname after ordering?
You can change the guest OS hostname anytime. The service label in billing may still show the original order value — contact support if you need billing-side updates or rDNS changes.
Should hostname match my domain?
Not required. Many admins use short internal names. Match FQDN only if you want consistency for mail/rDNS and you control the domain.
Where do I see my hostname after provisioning?
VPS Ready email, client-area service details, and inside the OS (hostname on Linux).
Related Articles
Need More Help?
DNS or hostname questions after ordering: open a ticket at billing.vpsgrid.net with service ID and the hostname you intended.
¿Le ha resultado útil esta respuesta?
