BIND_DNS

Check out the tty column. For each login there is either a tty number or pts number. pts stands for p suedo t erminal. These are the terminals to which people are connected. Notice that one person can be connected to multiple terminals using multiple shell sessions >>>>>>>>>>>>>>>>>

resolv.conf
/etc/resolv.conf is where Linux looks to find out how it should perform DNS lookups. The format is as follows: domain yourdomain.com search yourdomain.com otherdomains.com nameserver 192.168.10.1 nameserver 127.0.0.1

Pretty straight forward. The first line tells it what domain you are in. This can be omitted if you want, but I would recommend using it. The second line is a search pattern. This too can be omitted, but I would also recommend using it. Without it you could not do a lookup of a hostname without typing out it's fully qualified domain name. ie.. you couldn't lookup beavis. You'd have to lookup beavis.otherdomain.com. (Unless you specified this information in your /etc/hosts file) The "nameserver" lines tell it a search order for DNS servers. Now since we are setting up BIND on your system you will need to change this file. You'll want it to look more like the following: domain yourdomain.com search yourdomain.com nameserver 127.0.0.1 nameserver x.x.x.x

>>>>>>>>>>>>>>>>> 1. Each domain name is essentially just a path in a large inverted tree, called the **//domain namespace//** 2. The tree has a single root at the top.[*] In the Unix filesystem, this is called the **//root directory//** and is represented by a slash (/).

Each node in the tree has a text label (without dots) that can be up to 63 characters long. A null (zero-length) label is reserved for the root. The full domain name of any node in the tree is the sequence of labels on the path from that node to the root. Domain names are always read from the node toward the root ("up" the tree), with dots separating the names in the path.
 * Domain Names:**

A full list of DNS Record Types may be obtained from [|IANA DNS Parameters]. SOA A NS MX CNAME PTR
 * Resource Records:**


 * **RR** || **Value** || **RFC** || **Description** ||
 * [|A] || 1 || [|RFC 1035] || IPv4 Address record. An IPv4 address for a host. ||
 * [|AAAA] || 28 || [|RFC 3596] || IPv6 Address record. An IPv6 address for a host. Current IETF recommendation for IPv6 forward-mapped zones. ||
 * [|A6] || 38 || [|RFC 2874] || Experimental. Forward mapping of IPv6 addresses. An IP address for a host within the zone. ||
 * AFSDB || 18 || [|RFC 1183] || Location of AFS servers. Experimental - special apps only. ||
 * [|CNAME] || 5 || [|RFC 1035] || Canonical Name. An alias name for a host. ||
 * [|DNAME] || 39 || [|RFC 2672] || Experimental. Delegation of reverse addresses (primarily IPv6). ||
 * [|DNSKEY] || 48 || [|RFC 4034] || DNSSEC.bis. DNS public key RR. ||
 * [|DS] || 43 || [|RFC 4034] || DNSSEC.bis. Delegated Signer RR. ||
 * [|HINFO] || 13 || [|RFC 1035] || Host Information - optional text data about a host. ||
 * ISDN || 20 || [|RFC 1183] || ISDN address. Experimental = special applications only. ||
 * [|KEY] || 25 || [|RFC 2535] || Public key associated with a DNS name. ||
 * LOC || 29 || [|RFC 1876] || Stores GPS data. Experimental - widely used. ||
 * [|MX] || 15 || [|RFC 1035] || Mail Exchanger. A preference value and the host name for a mail server/exchanger that will service this zone. RFC 974 defines valid names. ||
 * [|NAPTR] || 35 || [|RFC 3403] || Naming Authority Pointer Record. Gross misnomer. General purpose definition of rule set to be used by applications e.g. VoIP ||
 * [|NS] || 2 || [|RFC 1035] || Name Server. Defines the authoritative name server(s) for the domain (defined by the SOA record) or the subdomain. ||
 * [|NSEC] || 47 || [|RFC 4034] || DNSSEC.bis. Next Secure record. Ssed to provide proof of non-existence of a name. ||
 * [|NXT] || 30 ||  || DNSSEC Next Domain record type. Obsolete use NSEC. ||
 * [|PTR] || 12 || [|RFC 1035] || IP address (IPv4 or IPv6) to host. Used in [|reverse maps]. ||
 * RP || 17 || [|RFC 1183] || Information about responsible person. Experimental - special apps only. ||
 * [|RRSIG] || 46 || [|RFC 4034] || DNSSEC.bis. Signed RRset. ||
 * RT || 21 || [|RFC 1183] || Through-route binding. Experimental - special apps only. ||
 * [|SIG] || 24 || [|RFC 2931]/[|/2535] || DNSSEC. Obsolete use RRSIG. SIG(0) is used as a special meta RR in DDNS and zone transfer security. ||
 * [|SOA] || 6 || [|RFC 1035] || Start of Authority. Defines the zone name, an e-mail contact and various time and refresh values applicable to the zone. ||
 * [|SPF] || 99 || [|RFC 4408] || Sender Policy Framework (v1). Defines the servers which are authorized to send mail for a domain. Its primary function is to prevent identity theft by spammers. ||
 * [|SRV] || 33 || [|RFC 2872] || Defines services available in the zone, for example, ldap, http etc.. ||
 * [|TXT] || 16 || [|RFC 1035] || Text information associated with a name. The [|SPF record should be defined using a TXT record] and may (as of April 2006) be defined using an SPF RR. DKIM ([|RFC 4871] also makes use of the TXT RR for authenticaing email. [|How to define DKIM/ADSP RRs]. ||
 * WKS || 11 || [|RFC 1035] || Well Known Services. Deprecated in favour of [|SRV]. ||
 * X25 || 19 || [|RFC 1183] || X.25 address. Experimental - special apps only. ||