FQDN (Fully Qualified Domain Name) is the complete domain name of a host, describing its exact position within the DNS hierarchy. For example, mail.example.com. points to a specific host called mail inside the example.com domain, not just to the domain itself. You'll run into this term when configuring a VPS, DNS, SSL certificates, mail servers, or remote access. It's easier to understand if you think of a domain name as an address: the more complete it is, the more precisely it tells you where to go.

What makes up an FQDN

Let's take an example: www.leneex.com.

Here, www is the hostname, leneex is the second-level domain, and com is the top-level domain, or TLD. The trailing dot matters too. In a full DNS record, it marks the root of the DNS hierarchy. The entry www.leneex.com. is technically fully qualified: there's no component after com, since what follows is the DNS root itself. The RFC describes a domain name as a sequence of labels ending with the root label. Regular interfaces and browsers usually hide that trailing dot. That's why you typically see "www.leneex.com", even though in a technical context you might encounter the full form www.leneex.com.

It's important not to confuse an FQDN with the domain itself.

  1. leneex.com — a domain name

  2. www.leneex.com — the name of a specific host within that domain

  3. mail.leneex.com — another host.

A single domain can contain many FQDNs.

FQDN vs. hostname vs. PQDN: what's the difference

The word "name" tends to cause confusion here. A hostname is the name of a host, like server1. An FQDN is the full name of a host including its domain part: server1.example.com. A PQDN (Partially Qualified Domain Name) is a name that isn't fully qualified and may need DNS context or a search suffix to resolve to a complete address.

Characteristic

FQDN

PQDN

Defines a position in DNS

Yes

No

Includes the domain part

Yes

May not

Example

server1.example.com

server1 or a name relative to a given domain

Depends on DNS context

No, when used as an absolute name

May depend on it

Typical use

SSL, DNS, mail, servers

Local work, referring to hosts within a domain

To put this in practice, picture a company's local network. An administrator types server1 and expects the system to figure out that this means server1.example.com. If the computer knows the relevant DNS suffix, that works. But server1.example.com already contains the full path — no guesswork required.

Where FQDN is used

FQDN matters wherever a system needs to unambiguously identify a specific host.

SSL certificates

An SSL certificate is issued for specific names. A certificate might be issued for shop.example.com. If the server is reachable under a different name, that name must be covered by the certificate through a SAN (Subject Alternative Name). When setting up HTTPS, it's important to know exactly which domain name the client will use.

Mail server

Mail infrastructure relies heavily on DNS names. A server might be named mail.example.com. Mail delivery also depends on MX records, and reverse DNS lookup via a PTR record can link an IP address back to the server's name. For a mail system, consistent DNS configuration is especially important: the server name, DNS records, and mail software settings all need to line up with each other.

Connecting to a server by name

Instead of an IP address, you can reach a server by its FQDN:

server.example.com

DNS maps this name to an IP address through the corresponding records. The most common option is an A record for IPv4 or an AAAA record for IPv6. If the name is an alias for another name, a CNAME record may be used instead.

When setting up a VPS, FQDN is often one of the first parameters you'll encounter. It can be used for the server's own hostname, SSL, and mail infrastructure. If you're deploying your own server and want to get hands-on with this kind of configuration, Leneex VPS is one infrastructure option where you can set all of this up yourself.

How to find your server's FQDN

On Linux, you can check the full hostname with:

hostname -f

or the equivalent long form:

hostname --fqdn

The hostname utility documents the -f/--fqdn option specifically as a way to print the system's FQDN. The result depends on the current hostname configuration and the name resolution mechanisms in place.

If the server is configured accordingly, the command may return server.example.com. If you get only a short name instead of the expected FQDN, or the command returns something unexpected, that doesn't mean Linux "doesn't support FQDN." Usually the issue lies in hostname settings, DNS, or local name-resolution files. To check a specific configuration, you need to look not just at the hostname itself, but also at how the system resolves that name.

FQDN limitations

DNS imposes limits on name length. RFC 1035 sets the maximum length of a single DNS label at 63 octets, and the full DNS name in the format used by the protocol is limited to 255 octets, including overhead bytes.

That said, Linux application documentation sometimes references a 253-character limit for a hostname without the trailing dot. This comes down to how the textual representation of the name is counted. For a regular server, the practical takeaway is simple: individual parts of the name shouldn't be excessively long, and the full name needs to fit within DNS limits.

FQDN is the complete address within DNS

FQDN serves one main purpose: to unambiguously name a specific host within the DNS hierarchy. server1 doesn't tell you much. server1.example.com tells you a lot more: it's the host server1, located within the example.com domain, which sits in the .com zone and ultimately under the DNS root. FQDN comes up wherever precision matters: in SSL, DNS, mail servers, RDP, and VPS configuration. If you're setting up a server for the first time and ran into FQDN in a control panel or a guide, the next step is to check out the VPS configurations on our site and see which server parameters are available for you to configure yourself.

FAQ

How does an FQDN differ from an IP address?

An FQDN is a text-based name for a host, like server.example.com, while an IP address is a numeric network address, like 203.0.113.10. DNS links the name to the IP address so users don't have to memorize the server's numeric address.

Is the trailing dot in an FQDN mandatory?

In an absolute DNS record, the trailing dot marks the DNS root and explicitly shows that the name is fully qualified. User interfaces often omit it, which is why server.example.com is typically written without it.

Can a server have more than one FQDN?

Yes. A single server can be reachable under several names, such as www.example.com, api.example.com, and mail.example.com, as long as DNS and the relevant software are configured to support that.

Does a regular shared-hosting website need an FQDN?

Owners of a typical website usually don't need to configure a server FQDN themselves. The hosting provider manages the server infrastructure, and the user only needs the site's domain name.

An A record maps a hostname to an IPv4 address. For example, DNS can map server1.example.com to a specific IPv4 address, after which applications can locate the server by its FQDN.