A fully qualified domain name (FQDN), sometimes also referred to as an absolute domain name, is a domain name that specifies its exact location in the tree hierarchy of the Domain Name System (DNS). It specifies all domain levels, including the top-level domain and the root zone. A fully qualified domain name is distinguished by its lack of ambiguity in terms of DNS zone location in the hierarchy of DNS labels: it can be interpreted only in one way.
A fully qualified domain name is conventionally written as a list of domain labels separated using the full stop “
.” character (dot or period). The top of the hierarchy in an FQDN begins with the rightmost label. For instance, in the FQDN
com is a label directly under the root zone,
example is nested under
com, and finally
somehost is nested under
The topmost layer of every domain name is the DNS root zone, which is expressed as an empty label and can be represented in an FQDN with a trailing dot, such as
somehost.example.com.. A trailing dot is generally implied and often omitted by most applications. Trailing dots are required by the standard format for DNS zone files, as well as to disambiguate cases where an FQDN does not contain any other label separators, such as the FQDNs for the root zone itself and any top-level domain.
Relative domain names
A relative domain name is a domain name which does not include all labels. It may also be referred to as a partially-qualified domain name, or PQDN. Hostnames can be used as relative domain names.
Dot-separated fully qualified domain names are the primarily used form for human-readable representations of a domain name. Dot-separated domain names are not used in the internal representation of labels in a DNS message but are used to reference domains in some TXT records and can appear in resolver configurations, system hosts files, and URLs.
Web addresses typically use FQDNs to represent the host, as it ensures the address will be interpreted identically on any network. Relative hostnames are allowed by some protocols, including HTTP, but disallowed by others, such as the Simple Mail Transfer Protocol (SMTP).
- Mockapetris, Paul. Domain names – Implementation and Specification. doi:10.17487/RFC1035. RFC 1035.
- April N. Marine; Joyce K. Reynolds; Gary Scott Malkin (March 1994). "Questions About the Domain Name System". Answers to Commonly asked "New Internet User" Questions. IETF. sec. 5. doi:10.17487/RFC1594. RFC 1594. Retrieved 29 April 2013.
If you think of the DNS as a tree-structure with each node having its own label, a fully qualified domain name for a specific node would be its label followed by the labels of all the other nodes between it and the root of the tree.
- RFC 2181
- Fisher, Tim. "FQDN". About.com. Archived from the original on 3 April 2013. Retrieved 20 March 2013.
- RFC 2181
- Gavron, Ehud (October 1993). "A Security Problem and Proposed Correction With Widely Deployed DNS Software". Archived from the original on 2020-10-17. Retrieved 2020-10-01.
- "Fully Qualified Domain Name (FQDN) and Partially Qualified Domain Name (PQDN)". Archived from the original on 2015-03-16. Retrieved 2015-03-23.
- "Wireshark Q&A". osqa-ask.wireshark.org. Archived from the original on 13 April 2021. Retrieved 13 April 2021.
- Klensin, John C. (1998-05-21). "Definition of domain names in Simple Mail Transfer Protocol". Tools.ietf.org. Archived from the original on 2013-12-30. Retrieved 2014-01-08.
- 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
- RFC 4703: Resolution of Fully Qualified Domain Name (FQDN) Conflicts among Dynamic Host Configuration Protocol (DHCP) Clients