Hostname

A hostname is the human-readable label assigned to a device or server on a network, such as mail.example.com. Hostnames are resolved to IP addresses through the Domain Name System (DNS), and back again through reverse DNS (rDNS) and PTR records.

For a mail server the hostname is not cosmetic. It is the identity the server presents to every other server it talks to, and it is checked.

What makes a hostname fully qualified?

A fully qualified domain name (FQDN) is a hostname that includes every label up to the top-level domain, so it is unambiguous no matter where it is resolved from:

mail . example . com
 |       |        |
 |       |        +-- top-level domain
 |       +----------- domain
 +------------------- host label

A mail server must use an FQDN — a bare mail, or a name that only resolves inside your own network, will fail on the receiving side. It also must resolve publicly: a hostname that only exists in /etc/hosts is not a hostname as far as the internet is concerned.

Where does the hostname appear in SMTP?

In the greeting. The connecting server announces itself with HELO or EHLO followed by its own hostname, before anything else happens:

$ telnet mx1.example.net 25
220 mx1.example.net ESMTP Postfix
EHLO mail.example.com
250-mx1.example.net
250-PIPELINING
250-SIZE 20480000
250-STARTTLS
250 8BITMIME

That name is recorded in the Received: header of every message the connection delivers, which is why it stays visible to the recipient and to any filter that inspects the header chain:

Received: from mail.example.com (mail.example.com [192.0.2.25])
	by mx1.example.net (Postfix) with ESMTPS id 4Rk8Zt1234
	for <recipient@example.net>; Tue, 04 Aug 2026 08:11:02 +0000

What is forward-confirmed reverse DNS?

Receiving servers do not take the greeting at face value. They perform a round trip, and the term for it is forward-confirmed reverse DNS (FCrDNS):

  1. Look up the PTR record for the connecting IP address.
  2. Look up the A or AAAA record for the hostname that PTR returned.
  3. Check that it resolves back to the same IP address.
$ dig -x 192.0.2.25 +short
mail.example.com.

$ dig a mail.example.com +short
192.0.2.25

When those agree, the hostname is confirmed. When they do not — a missing PTR record, a PTR pointing at a name with no forward record, or a forward record resolving somewhere else — the connection is treated as unverified, and many receivers reject or heavily penalise it. This is one of the most common causes of mail from an otherwise correctly configured server being refused.

Ideally all three agree: the HELO/EHLO name, the PTR record, and the forward record. They do not strictly have to be identical, but every difference is one more thing a receiving filter has to be lenient about.

What makes a bad hostname for a mail server?

Why do hostnames matter for blacklisting?

Blocklists and reputation systems key primarily on IP addresses rather than hostnames, for a simple reason: a hostname can be changed in minutes, while the IP address is what actually connects and is far harder to replace.

The hostname still matters, because it feeds the checks that happen before any reputation lookup. A missing or invalid PTR record is frequently enough on its own to have a connection refused, and a generic hostname raises the score of every message from that server. See IP blacklisting for how the listings themselves work, and PTR record for who controls the reverse entry and how to get it set.