A fully qualified domain name
) is an unambiguous domain name
that specifies the exact location in the Domain Name System
's tree hierarchy through to a top-level domain
and finally to the root domain
. Technically, a FQDN has a trailing dot
(for example: somehost.example.com.
), but most DNS resolvers
will treat any domain name that already has a dot as being an FQDN and add the final dot needed for the root of the DNS tree. Resolvers will treat a domain name without a dot as unqualified and automatically add a default domain name and the final dot. Some applications, such as web browsers
will try to qualify the domain name part of a Uniform Resource Locator
(URL) if the resolver can not find the domain. In other cases, such as DNS zone files
, the trailing dot is always required to denote a FQDN. An FQDN differs from a regular domain name
by its absoluteness; a default domain name will not be added. Note however that valid hostnames in email are not the same as valid DNS hostnames: email hostnames never
end with a dot.
For example, given a device with a local hostname of myhost and a default parent domain name of example.com, the fully qualified domain name is myhost.example.com. It therefore uniquely defines the device — whilst there might be many hosts in the world called myhost, there can only be one myhost.example.com.
There are situations in specific implementations of the Domain Name System, in which, for technical reasons, a fully qualified domain name must end with a full stop (dot), indicating the DNS root zone. This ensures that the name is intended to be fully qualified. For example myhost.bar.com could be ambiguous, as it may be just a hostname within another higher level domain, and because not all resolvers assume that domain names containing a dot are absolute. myhost.bar.com., with the dot appended, is an unambigous fully qualified domain name. In most practical uses, the trailing dot is not required.
- RFC 1035: Domain names: implementation and specification
- RFC 1123: Requirements for Internet Hosts - application and support
- RFC 1535: A Security Problem and Proposed Correction With Widely Deployed DNS Software
- RFC 2181: Clarifications to the DNS specification