99-523: In the Domain Name System (DNS) hierarchy, a subdomain is a domain that is a part of another (main) domain. For example, if a domain offered an online store as part of their website example.com , it might use the subdomain shop.example.com . The Domain Name System (DNS) has a tree structure or hierarchy, which includes nodes on the tree being a domain name . A subdomain is a domain that
198-446: A label and zero or more resource records (RR), which hold information associated with the domain name. The domain name itself consists of the label, concatenated with the name of its parent node on the right, separated by a dot. The tree sub-divides into zones beginning at the root zone . A DNS zone may consist of as many domains and subdomains as the zone manager chooses. DNS can also be partitioned according to class where
297-446: A label and zero or more resource records (RR), which hold information associated with the domain name. The domain name itself consists of the label, concatenated with the name of its parent node on the right, separated by a dot. The tree sub-divides into zones beginning at the root zone . A DNS zone may consist of as many domains and subdomains as the zone manager chooses. DNS can also be partitioned according to class where
396-480: A "com" server, and finally an "example.com" server. Name servers in delegations are identified by name, rather than by IP address. This means that a resolving name server must issue another DNS request to find out the IP address of the server to which it has been referred. If the name given in the delegation is a subdomain of the domain for which the delegation is being provided, there is a circular dependency . In this case,
495-435: A "com" server, and finally an "example.com" server. Name servers in delegations are identified by name, rather than by IP address. This means that a resolving name server must issue another DNS request to find out the IP address of the server to which it has been referred. If the name given in the delegation is a subdomain of the domain for which the delegation is being provided, there is a circular dependency . In this case,
594-408: A cache of data. An authoritative name server can either be a primary server or a secondary server. Historically the terms master/slave and primary/secondary were sometimes used interchangeably but the current practice is to use the latter form. A primary server is a server that stores the original copies of all zone records. A secondary server uses a special automatic updating mechanism in
693-408: A cache of data. An authoritative name server can either be a primary server or a secondary server. Historically the terms master/slave and primary/secondary were sometimes used interchangeably but the current practice is to use the latter form. A primary server is a server that stores the original copies of all zone records. A secondary server uses a special automatic updating mechanism in
792-416: A combination of these methods. In a non-recursive query , a DNS resolver queries a DNS server that provides a record either for which the server is authoritative, or it provides a partial result without querying other servers. In case of a caching DNS resolver , the non-recursive query of its local DNS cache delivers a result and reduces the load on upstream DNS servers by caching DNS resource records for
891-416: A combination of these methods. In a non-recursive query , a DNS resolver queries a DNS server that provides a record either for which the server is authoritative, or it provides a partial result without querying other servers. In case of a caching DNS resolver , the non-recursive query of its local DNS cache delivers a result and reduces the load on upstream DNS servers by caching DNS resource records for
990-728: A compromise between five competing proposals of solutions to Paul Mockapetris . Mockapetris instead created the Domain Name System in 1983 while at the University of Southern California . The Internet Engineering Task Force published the original specifications in RFC 882 and RFC 883 in November 1983. These were updated in RFC 973 in January 1986. In 1984, four UC Berkeley students, Douglas Terry, Mark Painter, David Riggle, and Songnian Zhou, wrote
1089-468: A compromise between five competing proposals of solutions to Paul Mockapetris . Mockapetris instead created the Domain Name System in 1983 while at the University of Southern California . The Internet Engineering Task Force published the original specifications in RFC 882 and RFC 883 in November 1983. These were updated in RFC 973 in January 1986. In 1984, four UC Berkeley students, Douglas Terry, Mark Painter, David Riggle, and Songnian Zhou, wrote
SECTION 10
#17328631249031188-399: A dataset from a reliable source. Assuming the resolver has no cached records to accelerate the process, the resolution process starts with a query to one of the root servers. In typical operation, the root servers do not answer directly, but respond with a referral to more authoritative servers, e.g., a query for "www.wikipedia.org" is referred to the org servers. The resolver now queries
1287-399: A dataset from a reliable source. Assuming the resolver has no cached records to accelerate the process, the resolution process starts with a query to one of the root servers. In typical operation, the root servers do not answer directly, but respond with a referral to more authoritative servers, e.g., a query for "www.wikipedia.org" is referred to the org servers. The resolver now queries
1386-1053: A domain, you can utilize a variety of methods and tools. Automated tools like Amass and Subfinder leverage open-source intelligence and SSL certificate data to quickly uncover subdomains. Google Dorking, using the "site:" operator, allows for manual searches of indexed subdomains, while brute force techniques systematically query DNS servers with potential names. Passive DNS reconnaissance through APIs from services like SecurityTrails & Subdomain Center can reveal historical data without direct queries. Additionally, community resources such as GitHub and Pastebin may contain publicly available lists of subdomains. Combining these approaches will enhance your ability to effectively identify hidden or overlooked subdomains for security assessments or research purposes. Subdomains are often used by internet service providers supplying web services. They allocate one (or more) subdomains to their clients who do not have their own domain name. This allows independent administration by
1485-526: A general purpose database, the DNS has also been used in combating unsolicited email (spam) by storing a real-time blackhole list (RBL). The DNS database is traditionally stored in a structured text file, the zone file , but other database systems are common. The Domain Name System originally used the User Datagram Protocol (UDP) as transport over IP. Reliability, security, and privacy concerns spawned
1584-416: A general purpose database, the DNS has also been used in combating unsolicited email (spam) by storing a real-time blackhole list (RBL). The DNS database is traditionally stored in a structured text file, the zone file , but other database systems are common. The Domain Name System originally used the User Datagram Protocol (UDP) as transport over IP. Reliability, security, and privacy concerns spawned
1683-469: A naming system for computers , services, and other resources on the Internet or other Internet Protocol (IP) networks. It associates various information with domain names ( identification strings ) assigned to each of the associated entities. Most prominently, it translates readily memorized domain names to the numerical IP addresses needed for locating and identifying computer services and devices with
1782-599: A part of the URL that can be routed to any file or folder on the server machine. Domain Name System Early research and development: Merging the networks and creating the Internet: Commercialization, privatization, broader access leads to the modern Internet: Examples of Internet services: The Domain Name System ( DNS ) is a hierarchical and distributed name service that provides
1881-407: A period of time after an initial response from upstream DNS servers. In a recursive query , a DNS resolver queries a single DNS server, which may in turn query other DNS servers on behalf of the requester. For example, a simple stub resolver running on a home router typically makes a recursive query to the DNS server run by the user's ISP . A recursive query is one for which the DNS server answers
1980-407: A period of time after an initial response from upstream DNS servers. In a recursive query , a DNS resolver queries a single DNS server, which may in turn query other DNS servers on behalf of the requester. For example, a simple stub resolver running on a home router typically makes a recursive query to the DNS server run by the user's ISP . A recursive query is one for which the DNS server answers
2079-485: A separate zone file with a SOA record (Start of Authority). Most domain registries only allocate a two-level domain name. Hosting services typically provide DNS Servers to resolve subdomains within that master domain. A fully qualified domain name consists of multiple parts. For example, take the English Misplaced Pages domain en.wikipedia.org . The en is a subdomain of wikipedia.org . Although wikipedia.org
SECTION 20
#17328631249032178-469: A service's location on the network to change without affecting the end users, who continue to use the same hostname. Users take advantage of this when they use meaningful Uniform Resource Locators ( URLs ) and e-mail addresses without having to know how the computer actually locates the services. An important and ubiquitous function of the DNS is its central role in distributed Internet services such as cloud services and content delivery networks . When
2277-469: A service's location on the network to change without affecting the end users, who continue to use the same hostname. Users take advantage of this when they use meaningful Uniform Resource Locators ( URLs ) and e-mail addresses without having to know how the computer actually locates the services. An important and ubiquitous function of the DNS is its central role in distributed Internet services such as cloud services and content delivery networks . When
2376-597: A structure where the domain contains administrative directories and files including the FTP directories and webpages. The FTP subdomain could contain logs and the web page directories, while the WWW subdomain contains the directories for the webpages. Independent authentication for each domain provides access control over the various levels of the domain. In the United Kingdom , the second-level domain names are standard and branch off from
2475-442: A time to live (TTL), which indicates how long the information remains valid before it needs to be discarded or refreshed. This TTL is determined by the administrator of the authoritative DNS server and can range from a few seconds to several days or even weeks. Resource record Early research and development: Merging the networks and creating the Internet: Commercialization, privatization, broader access leads to
2574-477: A type of error called a "lame delegation" or "lame response". Domain name resolvers determine the domain name servers responsible for the domain name in question by a sequence of queries starting with the right-most (top-level) domain label. For proper operation of its domain name resolver, a network host is configured with an initial cache ( hints ) of the known addresses of the root name servers. The hints are updated periodically by an administrator by retrieving
2673-477: A type of error called a "lame delegation" or "lame response". Domain name resolvers determine the domain name servers responsible for the domain name in question by a sequence of queries starting with the right-most (top-level) domain label. For proper operation of its domain name resolver, a network host is configured with an initial cache ( hints ) of the known addresses of the root name servers. The hints are updated periodically by an administrator by retrieving
2772-410: A user accesses a distributed Internet service using a URL, the domain name of the URL is translated to the IP address of a server that is proximal to the user. The key functionality of the DNS exploited here is that different users can simultaneously receive different translations for the same domain name, a key point of divergence from a traditional phone-book view of the DNS. This process of using
2871-410: A user accesses a distributed Internet service using a URL, the domain name of the URL is translated to the IP address of a server that is proximal to the user. The key functionality of the DNS exploited here is that different users can simultaneously receive different translations for the same domain name, a key point of divergence from a traditional phone-book view of the DNS. This process of using
2970-401: Is inappropriate to use the term "subdomain" to refer to any mapping other than that provided by zone NS (name server) records and any server-destination other than that. According to RFC 1034, "a domain is a subdomain of another domain if it is contained within that domain" . Based on that definition, a host cannot be a subdomain, only a domain can be a subdomain. A subdomain will also have
3069-489: Is known as the LDH rule (letters, digits, hyphen). Domain names are interpreted in a case-independent manner. Labels may not start or end with a hyphen. An additional rule requires that top-level domain names should not be all-numeric. The limited set of ASCII characters permitted in the DNS prevented the representation of names and words of many languages in their native alphabets or scripts. To make this possible, ICANN approved
Subdomain - Misplaced Pages Continue
3168-444: Is known as the LDH rule (letters, digits, hyphen). Domain names are interpreted in a case-independent manner. Labels may not start or end with a hyphen. An additional rule requires that top-level domain names should not be all-numeric. The limited set of ASCII characters permitted in the DNS prevented the representation of names and words of many languages in their native alphabets or scripts. To make this possible, ICANN approved
3267-484: Is only achieved with at least 6 labels (counting the last null label). Although no technical limitation exists to prevent domain name labels from using any character that is representable by an octet, hostnames use a preferred format and character set. The characters allowed in labels are a subset of the ASCII character set, consisting of characters a through z , A through Z , digits 0 through 9 , and hyphen. This rule
3366-437: Is only achieved with at least 6 labels (counting the last null label). Although no technical limitation exists to prevent domain name labels from using any character that is representable by an octet, hostnames use a preferred format and character set. The characters allowed in labels are a subset of the ASCII character set, consisting of characters a through z , A through Z , digits 0 through 9 , and hyphen. This rule
3465-613: Is part of a larger domain. Each label may contain from 0 to 63 octets . The full domain name may not exceed a total length of 253 ASCII characters in its textual representation. Subdomains are defined by editing the DNS zone file pertaining to the parent domain. However, there is an ongoing debate over the use of the term "subdomain" when referring to names which map to the Address record A (host) and various other types of zone records which may map to any public IP address destination and any type of server. Network Operations teams insist that it
3564-399: Is served by the root name servers , the servers to query when looking up ( resolving ) a TLD . An authoritative name server is a name server that only gives answers to DNS queries from data that have been configured by an original source, for example, the domain administrator or by dynamic DNS methods, in contrast to answers obtained via a query to another name server that only maintains
3663-399: Is served by the root name servers , the servers to query when looking up ( resolving ) a TLD . An authoritative name server is a name server that only gives answers to DNS queries from data that have been configured by an original source, for example, the domain administrator or by dynamic DNS methods, in contrast to answers obtained via a query to another name server that only maintains
3762-470: Is usually considered to be the domain name , wikipedia is actually a sub-domain of the org TLD (top level domain). Any fully qualified domain name can be a host or a subdomain. A domain name that does not include any subdomains is known as an apex domain , root domain , or bare domain . For example, wikipedia.org is the apex domain of Misplaced Pages, which redirects to the subdomain www.wikipedia.org . To discover more subdomains associated with
3861-532: The Internationalizing Domain Names in Applications (IDNA) system, by which user applications, such as web browsers, map Unicode strings into the valid DNS character set using Punycode . In 2009, ICANN approved the installation of internationalized domain name country code top-level domains ( ccTLD s) . In addition, many registries of the existing top-level domain names ( TLD s ) have adopted
3960-404: The Internationalizing Domain Names in Applications (IDNA) system, by which user applications, such as web browsers, map Unicode strings into the valid DNS character set using Punycode . In 2009, ICANN approved the installation of internationalized domain name country code top-level domains ( ccTLD s) . In addition, many registries of the existing top-level domain names ( TLD s ) have adopted
4059-745: The top-level domain . For example: A vanity domain is a subdomain of an ISP's domain that is aliased to an individual user account, or a subdomain that expresses the individuality of the person on whose behalf it is registered. Depending on application, a record inside a domain, or subdomain might refer to a hostname , or a service provided by a number of machines in a cluster. Some websites use different subdomains to point to different server clusters . For example, www.example.com points to Server Cluster 1 or Datacentre 1, and www2.example.com points to Server Cluster 2 or Datacentre 2 etc. Subdomains are different from directories. Directories are physical folders on an actual computer, while subdomains are
Subdomain - Misplaced Pages Continue
4158-478: The top-level domain ; for example, the domain name www.example.com belongs to the top-level domain com . The hierarchy of domains descends from right to left; each label to the left specifies a subdivision, or subdomain of the domain to the right. For example, the label example specifies a subdomain of the com domain, and www is a subdomain of example.com. This tree of subdivisions may have up to 127 levels. A label may contain zero to 63 characters, because
4257-478: The top-level domain ; for example, the domain name www.example.com belongs to the top-level domain com . The hierarchy of domains descends from right to left; each label to the left specifies a subdivision, or subdomain of the domain to the right. For example, the label example specifies a subdomain of the com domain, and www is a subdomain of example.com. This tree of subdivisions may have up to 127 levels. A label may contain zero to 63 characters, because
4356-404: The " Authoritative Answer " ( AA ) bit in its responses. This flag is usually reproduced prominently in the output of DNS administration query tools, such as dig , to indicate that the responding name server is an authority for the domain name in question. When a name server is designated as the authoritative server for a domain name for which it does not have authoritative data, it presents
4455-404: The " Authoritative Answer " ( AA ) bit in its responses. This flag is usually reproduced prominently in the output of DNS administration query tools, such as dig , to indicate that the responding name server is an authority for the domain name in question. When a name server is designated as the authoritative server for a domain name for which it does not have authoritative data, it presents
4554-526: The ARPANET. Elizabeth Feinler developed and maintained the first ARPANET directory. Maintenance of numerical addresses, called the Assigned Numbers List, was handled by Jon Postel at the University of Southern California 's Information Sciences Institute (ISI), whose team worked closely with SRI. Addresses were assigned manually. Computers, including their hostnames and addresses, were added to
4653-412: The ARPANET. Elizabeth Feinler developed and maintained the first ARPANET directory. Maintenance of numerical addresses, called the Assigned Numbers List, was handled by Jon Postel at the University of Southern California 's Information Sciences Institute (ISI), whose team worked closely with SRI. Addresses were assigned manually. Computers, including their hostnames and addresses, were added to
4752-462: The DNS database are for start of authority ( SOA ), IP addresses ( A and AAAA ), SMTP mail exchangers (MX), name servers (NS), pointers for reverse DNS lookups (PTR), and domain name aliases (CNAME). Although not intended to be a general purpose database, DNS has been expanded over time to store records for other types of data for either automatic lookups, such as DNSSEC records, or for human queries such as responsible person (RP) records. As
4851-462: The DNS database are for start of authority ( SOA ), IP addresses ( A and AAAA ), SMTP mail exchangers (MX), name servers (NS), pointers for reverse DNS lookups (PTR), and domain name aliases (CNAME). Although not intended to be a general purpose database, DNS has been expanded over time to store records for other types of data for either automatic lookups, such as DNSSEC records, or for human queries such as responsible person (RP) records. As
4950-401: The DNS protocol in communication with its primary to maintain an identical copy of the primary records. Every DNS zone must be assigned a set of authoritative name servers. This set of servers is stored in the parent domain zone with name server (NS) records. An authoritative server indicates its status of supplying definitive answers, deemed authoritative , by setting a protocol flag, called
5049-401: The DNS protocol in communication with its primary to maintain an identical copy of the primary records. Every DNS zone must be assigned a set of authoritative name servers. This set of servers is stored in the parent domain zone with name server (NS) records. An authoritative server indicates its status of supplying definitive answers, deemed authoritative , by setting a protocol flag, called
SECTION 50
#17328631249035148-417: The DNS to assign proximal servers to users is key to providing faster and more reliable responses on the Internet and is widely used by most major Internet services. The DNS reflects the structure of administrative responsibility on the Internet. Each subdomain is a zone of administrative autonomy delegated to a manager. For zones operated by a registry , administrative information is often complemented by
5247-417: The DNS to assign proximal servers to users is key to providing faster and more reliable responses on the Internet and is widely used by most major Internet services. The DNS reflects the structure of administrative responsibility on the Internet. Each subdomain is a zone of administrative autonomy delegated to a manager. For zones operated by a registry , administrative information is often complemented by
5346-456: The IDNA system, guided by RFC 5890, RFC 5891, RFC 5892, RFC 5893. The Domain Name System is maintained by a distributed database system, which uses the client–server model . The nodes of this database are the name servers . Each domain has at least one authoritative DNS server that publishes information about that domain and the name servers of any domains subordinate to it. The top of the hierarchy
5445-409: The IDNA system, guided by RFC 5890, RFC 5891, RFC 5892, RFC 5893. The Domain Name System is maintained by a distributed database system, which uses the client–server model . The nodes of this database are the name servers . Each domain has at least one authoritative DNS server that publishes information about that domain and the name servers of any domains subordinate to it. The top of the hierarchy
5544-430: The IP address spaces . The Domain Name System maintains the domain name hierarchy and provides translation services between it and the address spaces. Internet name servers and a communication protocol implement the Domain Name System. A DNS name server is a server that stores the DNS records for a domain; a DNS name server responds with answers to queries against its database. The most common types of records stored in
5643-430: The IP address spaces . The Domain Name System maintains the domain name hierarchy and provides translation services between it and the address spaces. Internet name servers and a communication protocol implement the Domain Name System. A DNS name server is a server that stores the DNS records for a domain; a DNS name server responds with answers to queries against its database. The most common types of records stored in
5742-402: The Internet, and increase performance in end-user applications, the Domain Name System supports DNS cache servers which store DNS query results for a period of time determined in the configuration ( time-to-live ) of the domain name record in question. Typically, such caching DNS servers also implement the recursive algorithm necessary to resolve a given name starting with the DNS root through to
5841-402: The Internet, and increase performance in end-user applications, the Domain Name System supports DNS cache servers which store DNS query results for a period of time determined in the configuration ( time-to-live ) of the domain name record in question. Typically, such caching DNS servers also implement the recursive algorithm necessary to resolve a given name starting with the DNS root through to
5940-543: The authoritative name servers of the queried domain. With this function implemented in the name server, user applications gain efficiency in design and operation. The combination of DNS caching and recursive functions in a name server is not mandatory; the functions can be implemented independently in servers for special purposes. Internet service providers typically provide recursive and caching name servers for their customers. In addition, many home networking routers implement DNS caches and recursion to improve efficiency in
6039-543: The authoritative name servers of the queried domain. With this function implemented in the name server, user applications gain efficiency in design and operation. The combination of DNS caching and recursive functions in a name server is not mandatory; the functions can be implemented independently in servers for special purposes. Internet service providers typically provide recursive and caching name servers for their customers. In addition, many home networking routers implement DNS caches and recursion to improve efficiency in
SECTION 60
#17328631249036138-454: The clients over their subdomain. Subdomains are also used by organizations that wish to assign a unique name to a particular department, function, or service related to the organization. For example, a university might assign "cs" to the computer science department, such that a number of hosts could be used inside that subdomain, such as www.cs.example.edu . There are some widely recognized subdomains such as WWW and FTP . This allows for
6237-466: The computer. Computers at educational institutions would have the domain edu , for example. She and her team managed the Host Naming Registry from 1972 to 1989. By the early 1980s, maintaining a single, centralized host table had become slow and unwieldy and the emerging network required an automated naming system to address technical and personnel issues. Postel directed the task of forging
6336-403: The computer. Computers at educational institutions would have the domain edu , for example. She and her team managed the Host Naming Registry from 1972 to 1989. By the early 1980s, maintaining a single, centralized host table had become slow and unwieldy and the emerging network required an automated naming system to address technical and personnel issues. Postel directed the task of forging
6435-438: The delegation for example.org. The glue records are address records that provide IP addresses for ns1.example.org. The resolver uses one or more of these IP addresses to query one of the domain's authoritative servers, which allows it to complete the DNS query. A common approach to reduce the burden on DNS servers is to cache the results of name resolution locally or on intermediary resolver hosts. Each DNS query result comes with
6534-438: The delegation for example.org. The glue records are address records that provide IP addresses for ns1.example.org. The resolver uses one or more of these IP addresses to query one of the domain's authoritative servers, which allows it to complete the DNS query. A common approach to reduce the burden on DNS servers is to cache the results of name resolution locally or on intermediary resolver hosts. Each DNS query result comes with
6633-738: The first Unix name server implementation for the Berkeley Internet Name Domain, commonly referred to as BIND . In 1985, Kevin Dunlap of DEC substantially revised the DNS implementation. Mike Karels , Phil Almquist, and Paul Vixie then took over BIND maintenance. Internet Systems Consortium was founded in 1994 by Rick Adams , Paul Vixie , and Carl Malamud , expressly to provide a home for BIND development and maintenance. BIND versions from 4.9.3 onward were developed and maintained by ISC, with support provided by ISC's sponsors. As co-architects/programmers, Bob Halley and Paul Vixie released
6732-617: The first Unix name server implementation for the Berkeley Internet Name Domain, commonly referred to as BIND . In 1985, Kevin Dunlap of DEC substantially revised the DNS implementation. Mike Karels , Phil Almquist, and Paul Vixie then took over BIND maintenance. Internet Systems Consortium was founded in 1994 by Rick Adams , Paul Vixie , and Carl Malamud , expressly to provide a home for BIND development and maintenance. BIND versions from 4.9.3 onward were developed and maintained by ISC, with support provided by ISC's sponsors. As co-architects/programmers, Bob Halley and Paul Vixie released
6831-453: The first production-ready version of BIND version 8 in May 1997. Since 2000, over 43 different core developers have worked on BIND. In November 1987, RFC 1034 and RFC 1035 superseded the 1983 DNS specifications. Several additional Request for Comments have proposed extensions to the core DNS protocols. The domain name space consists of a tree data structure . Each node or leaf in the tree has
6930-407: The first production-ready version of BIND version 8 in May 1997. Since 2000, over 43 different core developers have worked on BIND. In November 1987, RFC 1034 and RFC 1035 superseded the 1983 DNS specifications. Several additional Request for Comments have proposed extensions to the core DNS protocols. The domain name space consists of a tree data structure . Each node or leaf in the tree has
7029-433: The length is only allowed to take 6 bits. The null label of length zero is reserved for the root zone. The full domain name may not exceed the length of 253 characters in its textual representation (or 254 with the trailing dot). In the internal binary representation of the DNS this maximum length of 253 requires 255 octets of storage, as it also stores the length of the first of many labels and adds last null byte. 255 length
7128-433: The length is only allowed to take 6 bits. The null label of length zero is reserved for the root zone. The full domain name may not exceed the length of 253 characters in its textual representation (or 254 with the trailing dot). In the internal binary representation of the DNS this maximum length of 253 requires 255 octets of storage, as it also stores the length of the first of many labels and adds last null byte. 255 length
7227-422: The local network. The client side of the DNS is called a DNS resolver. A resolver is responsible for initiating and sequencing the queries that ultimately lead to a full resolution (translation) of the resource sought, e.g., translation of a domain name into an IP address. DNS resolvers are classified by a variety of query methods, such as recursive , non-recursive , and iterative . A resolution process may use
7326-422: The local network. The client side of the DNS is called a DNS resolver. A resolver is responsible for initiating and sequencing the queries that ultimately lead to a full resolution (translation) of the resource sought, e.g., translation of a domain name into an IP address. DNS resolvers are classified by a variety of query methods, such as recursive , non-recursive , and iterative . A resolution process may use
7425-476: The modern Internet: Examples of Internet services: The Domain Name System ( DNS ) is a hierarchical and distributed name service that provides a naming system for computers , services, and other resources on the Internet or other Internet Protocol (IP) networks. It associates various information with domain names ( identification strings ) assigned to each of the associated entities. Most prominently, it translates readily memorized domain names to
7524-408: The name server and IP address. For example, if the authoritative name server for example.org is ns1.example.org, a computer trying to resolve www.example.org first resolves ns1.example.org. As ns1 is contained in example.org, this requires resolving example.org first, which presents a circular dependency. To break the dependency, the name server for the top level domain org includes glue along with
7623-408: The name server and IP address. For example, if the authoritative name server for example.org is ns1.example.org, a computer trying to resolve www.example.org first resolves ns1.example.org. As ns1 is contained in example.org, this requires resolving example.org first, which presents a circular dependency. To break the dependency, the name server for the top level domain org includes glue along with
7722-409: The name server providing the delegation must also provide one or more IP addresses for the authoritative name server mentioned in the delegation. This information is called glue . The delegating name server provides this glue in the form of records in the additional section of the DNS response, and provides the delegation in the authority section of the response. A glue record is a combination of
7821-409: The name server providing the delegation must also provide one or more IP addresses for the authoritative name server mentioned in the delegation. This information is called glue . The delegating name server provides this glue in the form of records in the additional section of the DNS response, and provides the delegation in the authority section of the response. A glue record is a combination of
7920-613: The numerical IP addresses needed for locating and identifying computer services and devices with the underlying network protocols . The Domain Name System has been an essential component of the functionality of the Internet since 1985. The Domain Name System delegates the responsibility of assigning domain names and mapping those names to Internet resources by designating authoritative name servers for each domain. Network administrators may delegate authority over subdomains of their allocated name space to other name servers. This mechanism provides distributed and fault-tolerant service and
8019-532: The primary file by contacting the SRI Network Information Center (NIC), directed by Feinler, via telephone during business hours. Later, Feinler set up a WHOIS directory on a server in the NIC for retrieval of information about resources, contacts, and entities. She and her team developed the concept of domains. Feinler suggested that domains should be based on the location of the physical address of
8118-413: The primary file by contacting the SRI Network Information Center (NIC), directed by Feinler, via telephone during business hours. Later, Feinler set up a WHOIS directory on a server in the NIC for retrieval of information about resources, contacts, and entities. She and her team developed the concept of domains. Feinler suggested that domains should be based on the location of the physical address of
8217-402: The query completely by querying other name servers as needed. In typical operation, a client issues a recursive query to a caching recursive DNS server, which subsequently issues non-recursive queries to determine the answer and send a single answer back to the client. The resolver, or another DNS server acting recursively on behalf of the resolver, negotiates use of recursive service using bits in
8316-402: The query completely by querying other name servers as needed. In typical operation, a client issues a recursive query to a caching recursive DNS server, which subsequently issues non-recursive queries to determine the answer and send a single answer back to the client. The resolver, or another DNS server acting recursively on behalf of the resolver, negotiates use of recursive service using bits in
8415-404: The query headers. DNS servers are not required to support recursive queries. The iterative query procedure is a process in which a DNS resolver queries a chain of one or more DNS servers. Each server refers the client to the next server in the chain, until the current server can fully resolve the request. For example, a possible resolution of www.example.com would query a global root server, then
8514-404: The query headers. DNS servers are not required to support recursive queries. The iterative query procedure is a process in which a DNS resolver queries a chain of one or more DNS servers. Each server refers the client to the next server in the chain, until the current server can fully resolve the request. For example, a possible resolution of www.example.com would query a global root server, then
8613-472: The registry's RDAP and WHOIS services. That data can be used to gain insight on, and track responsibility for, a given host on the Internet. Using a simpler, more memorable name in place of a host's numerical address dates back to the ARPANET era. The Stanford Research Institute (now SRI International ) maintained a text file named HOSTS.TXT that mapped host names to the numerical addresses of computers on
8712-423: The registry's RDAP and WHOIS services. That data can be used to gain insight on, and track responsibility for, a given host on the Internet. Using a simpler, more memorable name in place of a host's numerical address dates back to the ARPANET era. The Stanford Research Institute (now SRI International ) maintained a text file named HOSTS.TXT that mapped host names to the numerical addresses of computers on
8811-516: The root servers, and as a result, root name servers actually are involved in only a relatively small fraction of all requests. In theory, authoritative name servers are sufficient for the operation of the Internet. However, with only authoritative name servers operating, every DNS query must start with recursive queries at the root zone of the Domain Name System and each user system would have to implement resolver software capable of recursive operation. To improve efficiency, reduce DNS traffic across
8910-516: The root servers, and as a result, root name servers actually are involved in only a relatively small fraction of all requests. In theory, authoritative name servers are sufficient for the operation of the Internet. However, with only authoritative name servers operating, every DNS query must start with recursive queries at the root zone of the Domain Name System and each user system would have to implement resolver software capable of recursive operation. To improve efficiency, reduce DNS traffic across
9009-629: The separate classes can be thought of as an array of parallel namespace trees. Administrative responsibility for any zone may be divided by creating additional zones. Authority over the new zone is said to be delegated to a designated name server. The parent zone ceases to be authoritative for the new zone. The definitive descriptions of the rules for forming domain names appear in RFC 1035, RFC 1123, RFC 2181, and RFC 5892. A domain name consists of one or more parts, technically called labels , that are conventionally concatenated , and delimited by dots, such as example.com. The right-most label conveys
9108-629: The separate classes can be thought of as an array of parallel namespace trees. Administrative responsibility for any zone may be divided by creating additional zones. Authority over the new zone is said to be delegated to a designated name server. The parent zone ceases to be authoritative for the new zone. The definitive descriptions of the rules for forming domain names appear in RFC 1035, RFC 1123, RFC 2181, and RFC 5892. A domain name consists of one or more parts, technically called labels , that are conventionally concatenated , and delimited by dots, such as example.com. The right-most label conveys
9207-423: The servers referred to, and iteratively repeats this process until it receives an authoritative answer. The diagram illustrates this process for the host that is named by the fully qualified domain name "www.wikipedia.org". This mechanism would place a large traffic burden on the root servers, if every resolution on the Internet required starting at the root. In practice caching is used in DNS servers to off-load
9306-423: The servers referred to, and iteratively repeats this process until it receives an authoritative answer. The diagram illustrates this process for the host that is named by the fully qualified domain name "www.wikipedia.org". This mechanism would place a large traffic burden on the root servers, if every resolution on the Internet required starting at the root. In practice caching is used in DNS servers to off-load
9405-513: The underlying network protocols . The Domain Name System has been an essential component of the functionality of the Internet since 1985. The Domain Name System delegates the responsibility of assigning domain names and mapping those names to Internet resources by designating authoritative name servers for each domain. Network administrators may delegate authority over subdomains of their allocated name space to other name servers. This mechanism provides distributed and fault-tolerant service and
9504-592: The use of the Transmission Control Protocol (TCP) as well as numerous other protocol developments. An often-used analogy to explain the DNS is that it serves as the phone book for the Internet by translating human-friendly computer hostnames into IP addresses. For example, the hostname www.example.com within the domain name example.com translates to the addresses 93.184.216.34 ( IPv4 ) and 2606:2800:220:1:248:1893:25c8:1946 ( IPv6 ). The DNS can be quickly and transparently updated, allowing
9603-521: The use of the Transmission Control Protocol (TCP) as well as numerous other protocol developments. An often-used analogy to explain the DNS is that it serves as the phone book for the Internet by translating human-friendly computer hostnames into IP addresses. For example, the hostname www.example.com within the domain name example.com translates to the addresses 93.184.216.34 ( IPv4 ) and 2606:2800:220:1:248:1893:25c8:1946 ( IPv6 ). The DNS can be quickly and transparently updated, allowing
9702-462: Was designed to avoid a single large central database. In addition, the DNS specifies the technical functionality of the database service that is at its core. It defines the DNS protocol, a detailed specification of the data structures and data communication exchanges used in the DNS, as part of the Internet protocol suite . The Internet maintains two principal namespaces , the domain name hierarchy and
9801-412: Was designed to avoid a single large central database. In addition, the DNS specifies the technical functionality of the database service that is at its core. It defines the DNS protocol, a detailed specification of the data structures and data communication exchanges used in the DNS, as part of the Internet protocol suite . The Internet maintains two principal namespaces , the domain name hierarchy and
#902097