Skip to content
AdminKit

FQDN

What is FQDN?

A fully qualified domain name (FQDN) specifies a host's exact position in the DNS hierarchy, from the host down to the root, per the naming rules RFC 1035 defines. Resolution reads each label right to left starting at the DNS root servers. AdminKit's DNS lookup tool validates the FQDN you enter before forwarding the query to its upstream resolver.

By AdminKit team, Netbase JSC · Updated

A fully qualified domain name (FQDN) specifies a host’s exact, complete position in the DNS hierarchy — for example www.example.com — rather than a partial or relative name a local resolver would need to guess a suffix for. NIST’s CSRC glossary defines it in similar terms, as an unambiguous identifier that contains every domain level, including the top-level domain. Microsoft’s Active Directory naming conventions give the practical size limits: 63 bytes per label and 255 bytes for the whole FQDN. DNS names are defined by RFC 1035, which specifies how a name is built from labels separated by dots, read right to left from the DNS root servers down to the specific host; an FQDN includes every label needed to resolve unambiguously from the root, conventionally written with a trailing dot to make that explicit, though most software omits it. Entering anything less than a full FQDN into a DNS tool — just “example” instead of “example.com” — either fails outright or resolves against a local search-domain suffix that has nothing to do with the intended target. AdminKit’s DNS lookup tool validates the FQDN you enter before forwarding the query to its upstream resolver. A label containing non-ASCII characters has to be converted to its ASCII-compatible Punycode form before it can appear in an FQDN at all, since DNS labels are ASCII-only on the wire.

FQDN is part of AdminKit’s DNS cluster; the full AdminKit glossary lists other related terms.

Frequently asked questions

Which direction does DNS resolution read an FQDN's labels?

Right to left, starting at the DNS root servers and working down through each parent zone to the specific host -- the opposite order from how the name is written.

What happens if you enter a partial name instead of a full FQDN?

It either fails outright or resolves against a local search-domain suffix that has nothing to do with the intended target -- entering "example" instead of "example.com" is a common version of this mistake.

Why is an FQDN sometimes written with a trailing dot?

The trailing dot makes explicit that every label needed to resolve unambiguously from the DNS root is present, though most software omits it in everyday use.

Can an FQDN contain non-ASCII characters directly?

No -- a label containing non-ASCII characters has to be converted to its ASCII-compatible Punycode form before it can appear in an FQDN at all, since DNS labels are ASCII-only on the wire.