• Choose a category
• All
• Classic-Fiction

On-line resources

The FAQ for comp.sys.tcp-ip.domains includes a lot of BIND information, mostly about BIND 4. It’s maintained by Chris Peckham and is available from

http://www.intac.com/~cdp/cptd-faq

The DNS Resources Directory, www.dns.net/dnsrd, is a useful collection of resources and pointers to resources maintained by András Salamon.

The RFCs

The RFCs that define the DNS system are available from www.rfc-editor.org. Early and evolving ideas appear first in the Internet-Drafts series and later move into the RFC series. A selected subset of the RFCs, including those that have caused BIND 9 to be such a major undertaking, are listed below.

The original, definitive standards

• 1034 – Domain Names: Concepts and Facilities

• 1035 – Domain Names: Implementation and Specification.

Proposed standards

• 1995 – Incremental Zone Transfer in DNS

• 1996 – A Mechanism for Prompt Notification of Zone Changes

• 2136 – Dynamic Updates in the Domain Name System

• 2181 – Clarifications to the DNS Specification

• 2308 – Negative Caching of DNS Queries

Newer standards-track RFCs

• 2535 – Domain Name System Security Extensions

• 2671 – Extension Mechanisms for DNS (EDNS0)

• 2672 – Non-Terminal DNS Name Redirection (DNAME)

• 2673 – Binary Labels in the Domain Name System

Miscellaneous RFCs

• 1535 – A Security Problem ... with Widely Deployed DNS Software

• 1536 – Common DNS Implementation Errors and Suggested Fixes

• 1982 – Serial Number Arithmetic

• 2536–2541 – Various DNSSEC RFCs

Resource record types

• 1183 – New DNS RR Definitions: AFSDB, RP, X25, ISDN, RT

• 1706 – DNS NSAP Resource Records

• 1876 – A Means for Expressing Location Information in DNS

• 2052 – A DNS RR for Specifying the Location of Services (SRV)

• 2168 – Resolution of Uniform Resource Identifiers using DNS

• 2230 – Key Exchange Delegation Record for the DNS

DNS and the Internet

• 1101 – DNS Encoding of Network Names and Other Types

• 1123 – Requirements for Internet Hosts: Application and Support

• 1591 – Domain Name System Structure and Delegation

• 2317 – Classless in-addr.arpa Delegation

DNS operations

• 1537 – Common DNS Data File Configuration Errors

• 1912 – Common DNS Operational and Configuration Errors

• 2182 – Selection and Operation of Secondary DNS Servers

• 2219 – Use of DNS Aliases for Network Services

Other DNS-related RFCs

• 1464 – Using DNS to Store Arbitrary String Attributes

• 1713 – Tools for DNS debugging

• 1794 – DNS Support for Load Balancing

• 2240 – A Legal Basis for Domain Name Allocation

• 2345 – Domain Names and Company Name Retrieval

• 2352 – A Convention for Using Legal Names as Domain Names

17 The Network File System

The Network File System, commonly known as NFS, allows you to share filesystems among computers. NFS is almost transparent to users and is “stateless,” meaning that no information is lost when an NFS server crashes. Clients can simply wait until the server returns and then continue as if nothing had happened.

NFS was introduced by Sun Microsystems in 1985. It was originally implemented as a surrogate filesystem for diskless clients, but the protocol proved to be well designed and very useful as a general file-sharing solution. In fact, it’s difficult to remember what life was like before NFS. All UNIX vendors provide a version of NFS; many use code licensed from Sun.

17.1 GENERAL INFORMATION ABOUT NFS

NFS consists of a number of components, including a mounting protocol and mount server, daemons that coordinate basic file service, and several diagnostic utilities. A portion of both the server-side and client-side software resides in the kernel. However, these parts of NFS need no configuration and are largely transparent from an administrator’s point of view.

NFS protocol versions

The NFS protocol has been remarkably stable over time. The original public release of NFS was version 2. In