Curriculum Design and Instruction To Teach
Linux Administration: Networking: DNS: The
Domain Name System:
Author: Charles Hayes:
This curriculum design and
instruction is for the Linux
administrator who must
efficiently solve technical
problems and maximize the
reliability and performance
of a production environment.
It addresses today's most
important Linux distributions
and most powerful new administrative
tools. It spells out detailed best
practices for every facet of system
administration, including storage
management, network design and
administration, web hosting,
software configuration management,
performance analysis, Windows
interoperability,m and much more.
Systems administrators will expecially
appreciate the thourough and up-to-date
subject of such topics such as DNS, LDAP,
secrutiy, and the Management of IT service
organizations:
Special Features Include:
* Phases For Conducting A Needs Assessment:
* Curriculum Design Supplement:
* Curriculum Design Plan:
* Lesson Plans:
* Instructional Goals:
* Instructional Objectives:
* Instructional Activities:
* Instructional Evaluation Techniques:
* Standard Vocabulary:
* A Limited Glimpse:
Topics Include:
* Networking:
@ DNS: The Domain Name System:
A. Introduction:
B. DNS for the impatient: adding a new machine:
C. The history of DNS:
1. BIND implementations:
2. Other implementations of DNS:
D. Who needs DNS?
E. The DNS namespace:
1. Masters of their domains:
2. Selecting a domain name:
3. Domain bloat:
4. Registering a second-level domain name:
5. Creating your own subdomains:
F. How DNS works:
1. Delegation:
2. Caching and efficiency:
3. The extended DNS protocol:
G. What's new in DNS:
H. The DNS database:
1. Resource records:
2. The SOA record:
3. NS records:
4. PTR records:
5. MX records:
6. CNAME records:
7. The CNAME hack:
8. LOC records:
9. SRV records:
10. TXT records:
11. IPv6 resource records:
12. IPv6 forward records:
13. IPv6 reverse records:
14. Security-related records:
15. Commands in zone files:
16. Glue records: links between zones:
I. The BIND software:
1. Versions of BIND:
2. Finding out what version you have:
3. Components of BIND:
4. named: the BIND name server:
5. Authoritative and caching-only servers:
6. The resolver library:
7. Shell interfaces to DNS:
J. Designing your DNS environment:
1. Namespace management:
2. Authoritative servers:
3. Caching servers:
4. Security:
5. Summing up:
6. A taxonomy of DNS/BIND chores:
K. BIND client issues:
1. Resolver configuration:
2. Resolver testing:
3. Impact on the rest of the system:
L. Bind server Configuration:
1. Hardware requirements:
2. Configuration files:
3. The include statement:
4. The options statement:
5. The acl statement:
6. The key statement:
7. The trusted-Keys statement:
8. The server statement:
9. The masters statement:
10. The Logging statement:
11. The zone statement:
12. The controls statement:
13. Split DNS and the view statement:
M. BIND configuration examples:
1. The localhost zone:
2. A small security company:
3. The Internet Systems Consortium, isc.org:
N. Starting named:
O. Updating zone files:
1. Zone transfers:
2. Dynamic updates:
P. Security issues:
1. Access control lists revisited:
2. Confining named:
3. Secure server-to-server communication
with TSIG and TKEY:
4. DNSSEC:
5. Negative answers:
6. Microsoft and DNS:
Q. Testing and debugging:
1. Logging:
2. Sample logging configuration:
3. Debug levels:
4. Debugging with rndc:
5. Lame delegations:
6. doc: domain obscenity control:
7. Other DNS sanity checking tools:
8. Performance issues:
R. Distribution specifics:
S. Recommended reading:
T. Mailing lists and newsgroups:
U. Books and other documentation:
V. On-line resources:
W. The RFCs:
* STATE OF THE ART CURRICULUM DESIGN:
* NEW:
* REFERENCES:
* ILLUSTRATIONS:
* PHOTOS:
* PAPERBACK:
* TRANSPARENT FRONT PAGE:
* TITLE PAGE:
* BLACK OR WHITE BACK PAGE COVER:
* 8 TO 10 INCH FONTS:
* BINDED: B OR W OR COLOR COIL: WIRE-0:
* 250 WHITE PAGES: 8x11 INCHES:
* ALLOW 10 TO 14 DAYS TO RECEIVE ITEM:
* ORDER EARLY WHILE SUPPLIES LAST:
