| Acronym |
Full form |
|
|
Acronym: IP
|
Internet Protocol
|
s two principal namespaces, the domain name hierarchy RFC 1034, ''Domain Names - Concepts and Facilities'', P. Mockapetris, The Internet Society (November 1987) and the Internet Protocol (IP) address system. RFC 781, ''Internet Protocol - DARPA Internet Program Protocol Specification'', Information Sciences Institute, J. Postel (Ed.), The Internet Society (September 1981) The Domain Name |
|
|
Acronym: TTL
|
time to live
|
ing and subsequent consultation of the copy instead of initiating a new request upstream. The time for which a resolver caches a DNS response is determined by a value called the time to live (TTL) associated with every record. The TTL is set by the administrator of the DNS server handing out the authoritative response. The period of validity may vary from just seconds to days or even weeks. |
|
|
Acronym: TCP
|
Transmission Control Protocol
|
rst=P |date=November 1987}} to serve requests. DNS queries consist of a single UDP request from the client followed by a single UDP reply from the server. The Transmission Control Protocol (TCP) is used when the response data size exceeds 512 bytes, or for tasks such as zone transfers. Some operating systems, such as HP-UX, are known to have resolver implementations |
|
|
Acronym: EDNS
|
Extension mechanisms for DNS
|
ns== The original DNS protocol had limited provisions for extension with new features. In 1999, Paul Vixie published in RFC 2671 an extension mechanism, called Extension mechanisms for DNS (EDNS) that introduced optional protocol elements without increasing overhead when not in use. This was accomplished through the OPT pseudo-resource record that only exists in wire transmissions of the pr |
|
|
Acronym: ICANN
|
Internet Corporation for Assigned Names and Numbers
|
. ==Domain name registration== The right to use a domain name is delegated by domain name registrars which are accredited by the Internet Corporation for Assigned Names and Numbers (ICANN), the organization charged with overseeing the name and number systems of the Internet. In addition to ICANN, each top-level domain (TLD) is maintained and serviced technically by an administrative or |
|
|
Acronym: IANA
|
Internet Assigned Numbers Authority
|
st top-level domains is delegated to responsible organizations by the Internet Corporation for Assigned Names and Numbers (ICANN), which operates the Internet Assigned Numbers Authority (IANA) and is in charge of maintaining the DNS root zone. Originally, the top-level domain space was organized into three main groups, RFC 920, ''Domain Requirements'', J. Postel, J. Reynolds, The In |
|
|
Acronym: IP
|
Internet Protocol
|
et]]. The most important function of these DNS servers is the translation (resolution) of humanly memorable domain names and hostnames into the corresponding numeric Internet Protocol (IP) addresses, the second principal Internet name space, used to identify and locate computer systems and resources on the Internet. ==Domain Name System== The Internet maintains two principal [[na |
|
|
Acronym: ICANN
|
Internet Corporation for Assigned Names and Numbers
|
top hierarchy of the Internet Domain Name System is served by the root name servers maintained by delegation by the Internet Corporation for Assigned Names and Numbers (ICANN). ===Authoritative name server=== An ''authoritative'' name server is a name server that gives #Authoritative answer|answers that have been configured by an original source, for example the do |
|
|
Acronym: LDAP
|
Lightweight Directory Access Protocol
|
ks)|broadcast]] algorithm. ==See also== * Comparison of DNS server software * Directory service * DNS Security Extensions (DNSSEC) * Lightweight Directory Access Protocol (LDAP) * Network Information Service (NIS) * Name Service Switch (NSS) * Resolver (DNS)|resolver, resolv.conf, resolvconf for Unix/Linux * BIND * OpenDNS * [[Google |
|
|
Acronym: NSS
|
Name Service Switch
|
oftware]] * Directory service * DNS Security Extensions (DNSSEC) * Lightweight Directory Access Protocol (LDAP) * Network Information Service (NIS) * Name Service Switch (NSS) * Resolver (DNS)|resolver, resolv.conf, resolvconf for Unix/Linux * BIND * OpenDNS * Google_Public_DNS| Google Public DNS ==References== ==External links== |
|
|
Acronym: SIP
|
Session Initiation Protocol
|
Domain names are also used as simple identification labels to indicate ownership or control of a resource. Such examples are the realm identifiers used in the Session Initiation Protocol (SIP), the DomainKeys used to verify DNS domains in e-mail systems, and in many other Uniform Resource Identifiers (URIs). An important purpose of domain names is to provide easily recogniza |
|
|
Acronym: ICANN
|
Internet Corporation for Assigned Names and Numbers
|
. ==Domain name registration== The right to use a domain name is delegated by domain name registrars which are accredited by the Internet Corporation for Assigned Names and Numbers (ICANN), the organization charged with overseeing the name and number systems of the Internet. In addition to ICANN, each top-level domain (TLD) is maintained and serviced technically by an administrative or |
|
|
Acronym: ICANN
|
Internet Corporation for Assigned Names and Numbers
|
astructure component for which VeriSign was the steward. Despite widespread criticism, VeriSign only reluctantly removed it after the Internet Corporation for Assigned Names and Numbers (ICANN) threatened to revoke its contract to administer the root name servers. ICANN published the extensive set of letters exchanged, committee reports, and ICANN decisions. {{cite web |last = Internet Cor |
|