|Front | Info | Lists | Newsfeeds | Study Guide | What is BSD?|
This is the BSDA Study Guide Book written via a wiki collaboration. This is a work in progress. You may contribute to or discuss this specific page at http://bsdwiki.reedmedia.net/wiki/Understand_various___34__domain__34___contexts.html.
Understand various "domain" contexts
Author: Ivan Voras IvanVoras FreeBSD
The term "domain" is used in Unix for several facilities. Understand the meaning of the term in the context of the Network Information System (NIS), the Domain Name System (DNS), Kerberos, and NTLM domains.
TODO: should this briefly mention the UNIX-domain protocol for local (on-machine) interprocess communication (because it is also called "domain")?
All "domains" that we're dealing with here are different ways of grouping certain types of information together. In particular:
DNS name are hierarchical and nested; thus the name:
refers to a machine called "www" in the domain "servers.example.com" which is nested in "example.com" which is itself nested under ".com". The
Note that high traffic sites have multiple computers answering to the same DNS name, in order to help performance (as demonstrated in the above example). DNS databases actually contain several types of records. The most common are "A" records which are widely used to access generic resources, but arguably equally popular are "MX" records that hold addresses of e-mail servers for specific domains:
A Windows NT domain (NTLM) name is formed by two backlashes followed by a case-insensitive name containing no spaces, for example:
Computers and users on the NTLM domain can be referenced either by appending a backslash and the username to the domain name or by using the (misused in this case) standard unix notation user@domain:
TODO: I don't understand this "misused".
domainname(1), resolv.conf(5), krb5.conf(5), smb.conf(5)