Do I need to restart anything after changing the hostname?

Yes. Reconnect your SSH session so the shell picks up the new prompt, and restart your mail server (Postfix or Exim) so it re-reads the new hostname for SMTP handshakes. On cPanel, changing the hostname through WHM's Networking Setup restarts the relevant services automatically.

Can I just use my main domain as the server hostname?

You can, but it's not recommended once you're running cPanel/WHM, since the hostname is meant to be a dedicated identity for the server itself, separate from any domain you host on it. Using a subdomain like server1.yourdomain.com avoids conflicts later.

What if my provider won't let me set a PTR record?

Ask their support team directly. Reverse DNS is tied to IP ownership, so only the provider controls it, but nearly all VPS and dedicated server providers offer it through a support ticket even if it's not exposed in the control panel UI.

My hostname and PTR match, but mail still bounces. What else could it be?

Check whether outbound port 25 is blocked (common on VPS providers to fight spam; you'll need to request it be opened or use an SMTP relay), and check your IP's reputation on a blacklist checker like MXToolbox.

Does this affect SSL certificates too?

Yes. WHM/cPanel issue an AutoSSL certificate for the hostname itself so the panel and services like webmail can present a valid certificate. An unresolvable or mismatched hostname can cause that certificate issuance to fail.

VPS Hostname & FQDN Setup Guide

You've done everything the deliverability checklists tell you to: SPF passes, DKIM passes, DMARC is set to p=quarantine, and your host even set up a PTR record for you. Mail from your VPS still bounces, or WHM keeps nagging about a hostname that isn't fully qualified. Nine times out of ten, the piece nobody checks is the server's own hostname — and it's set in about four places, not one.

Symptom: what you'll actually see

This shows up in a handful of ways depending on what's running on the box:

Sending mail bounces with 504 5.5.2 <localhost>: Helo command rejected: need fully-qualified hostname
telnet localhost 25 shows Postfix or Exim answering as 220 localhost.localdomain ESMTP instead of your real domain
WHM's initial setup wizard (or Server Configuration > Basic WebHost Manager Setup) warns the hostname isn't fully qualified, or AutoSSL fails to issue a certificate for the hostname itself
hostname -f returns just vps, an ISP-assigned string like static.123.45.67.89.yourprovider.com, or nothing at all
cPanel license activation or WHM API calls fail with vague hostname-resolution errors

If you've already ruled out SPF/DKIM/DMARC and confirmed the PTR record for your IP resolves correctly, this is almost always the next thing to check.

Cause: the server never got a real, matching hostname

Most VPS images ship with a placeholder hostname — localhost.localdomain, or something your provider generated at spin-up time like vmi123456.contabo.host. Nobody ever changes it, because the server works fine for browsing and SSH either way. Mail servers are the exception: Postfix and Exim announce themselves using the machine's hostname during the SMTP handshake (the HELO/EHLO line), and receiving servers check that name against reverse DNS. If the two don't match — or the hostname isn't even a real, resolvable domain — you get flagged or rejected outright.

There's also a naming trap specific to cPanel/WHM: the server's hostname should not be the same as any domain you plan to host on it. A common mistake is setting the hostname to a domain like yourdomain.com and then adding that same domain as a hosted account later — this creates a conflict because cPanel expects the hostname to be its own dedicated FQDN, separate from every account it hosts (e.g. server1.yourdomain.com, or a completely different domain used only for server identification).

The hostname actually lives in three separate places, and all three need to agree:

Where	What it controls
`/etc/hostname`	The persistent hostname the OS loads on boot
`/etc/hosts`	Local name resolution — maps the hostname to an IP without needing DNS
Postfix/Exim config (`myhostname`)	What the mail server actually announces in SMTP handshakes

Fix: set it correctly, in order

1. Pick a proper FQDN

Choose a hostname that's a real, fully-qualified domain you control and don't intend to host as a regular site — something like server1.yourdomain.com or a subdomain dedicated to infrastructure. Avoid single-word names like vps or server; a FQDN always has at least one dot.

2. Point DNS at it

Create an A record for that FQDN pointing to the server's public IP:

server1.yourdomain.com.  A  <your-vps-ip>

Then ask your VPS or hosting provider to set the reverse DNS (PTR) for that IP to the same FQDN. This is the piece that lives with the IP block, not your domain's zone — you can't set it yourself from cPanel's Zone Editor. Most providers have a Reverse DNS or PTR field in the network/IP section of their control panel; if you don't see one, open a support ticket and ask them to set it.

3. Set the hostname on the server

On the VPS itself (SSH in as root):

hostnamectl set-hostname server1.yourdomain.com

Then edit /etc/hosts so the FQDN resolves locally even before DNS is checked:

<your-vps-ip>  server1.yourdomain.com  server1

Log out and back in, then confirm both forms resolve correctly:

hostname -f   # should print the full FQDN
hostname -s   # should print just the short name

4. If you're running cPanel/WHM

Go to WHM > Networking Setup > Change Hostname, enter the FQDN, and save — WHM handles updating the underlying config and restarting the affected services for you. If you set the hostname manually via SSH first, changing it again through WHM afterward keeps cPanel's internal records in sync; don't skip this step even if hostnamectl already worked.

5. Confirm Postfix/Exim picked it up

postconf -n | grep myhostname
systemctl restart postfix   # or: /scripts/restartsrv_exim on cPanel

Then re-test the handshake:

telnet localhost 25

You should now see your real FQDN in the 220 banner instead of localhost.localdomain. Send a test email to a Gmail or Outlook address and check the message headers — the HELO/EHLO name should match your PTR record exactly.

Prevention

Practice	Why it matters
Set the hostname in the first hour after provisioning, before installing mail or cPanel	Avoids re-running setup wizards and license checks that already cached the old hostname
Never reuse a hosted domain as the server hostname	Prevents cPanel account/hostname conflicts down the line
Keep hostname, A record, and PTR record identical, character for character	Any mismatch is exactly what spam filters check for first
Re-verify after any OS reinstall or provider migration	Reimaging a VPS often resets `/etc/hostname` back to a generic default

If mail deliverability is still shaky after the hostname, PTR record, SPF, DKIM, and DMARC all line up, the remaining suspects are usually IP reputation (check it on MXToolbox) or port 25 being blocked outbound by your provider — both separate issues from what's covered here.

VPS Hostname & FQDN: Why Mail and cPanel Care How It's Set