Les Bell has taken EXCELLENT action against developing the preliminary DNS
objectives. He has reviewed the task list for completion, filling in gaps
in the current task list and implementing them into the objectives. His
files are attached.
Please review and commen as previously requested :)
Thank-you Les!
-Kara
---------- Forwarded message ----------
Date: Mon, 4 Jun 2001 12:45:34 -0500 (CDT)
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Preliminary Kernel Objectives
In order to assist in speedy objective development, I've tried to start
developing some preliminary objectives for our tasks, based on the most
recent organizational structure. (I've only received one response to the
last thread on organizing!)
The objectives are definitely not complete in current form, nor are they
the concrete foundation we're forced to work with. The tasks are our
foundation (also attached). The goal is to create objectives which cover
these tasks and fill in the technical gaps and details.
Our Level 1 objectives
(http://www.lpi.org/http://www.lpi.org/p-obj-101.html and p-obj-102.html)
should provide a good outline for what form and style objectives should be
written in. I've modified slightly (including bullets for specified files
and tools covered) but the rest should be developed in the same fashion as
the current Level 1 objectives. There's no need to obsess over this step
at this stage, as I plan to have this completed in a stage of formal
review.
I would like either comments, changes, and additions as well as assistance
completing (technically) the objectives I've posted; your comments and
submissions for replacement or additional objectives; and your comments
for supplementary objectives (if any).
Please begin by reviewing the current objectives for Level 1 at the URLs
listed above. Next review the task file for this group. Finally, review
the preliminary objectives file and comment. Please note that the
preliminary objectives file associates the current task numbers with the
affiliated objective. Please continue to refer to these task IDs when
commenting, reorganizing, etc. objectives.
I will continue submitting preliminary objective files for various
categories today and tomorrow. I would like good discussion and progress
toward finalizing objectives in progress by Wednesday. By Friday, those of
you interested in the contract positions to finalize objectives should be
able to begin review. By next week, I would like to publish our objectives
for public review and begin collecting preliminary items.
The next 10 days are going to be crazy, and I greatly appreciate your time
and dedication to development. We are moving extremely quickly, and
everyone is very excited about our current developments!
Please contact me if you are available 6/8 - 6/12 for contract objective
review and development. I apologize that this will encompass a weekend,
but it is necessary for succeeding with our current development schedule.
Slots are filling for the Item Writing session planned for the week of
June 18. If you had hoped to participate in this event, please contact me
to discuss availability, expenses, etc. It is likely that a two team
approach (6/18 - 6/20, 6/20 - 6/22) will be used, allowing for flexible
travel arrangements.
--
Kara Pritchard Phone: 618-398-7360
Author, RHCE Exam Cram
Director of Exam Development http://www.lpi.org/
Site Manager http://www.LinuxUsersGroups.org/
--
[3.1.7, 3.1.12, 3.1.16, 3.1.17, 3.1.18]
Obj: Basic BIND configuration.
The candidate should be able to: configure a BIND to function as a
caching-only DNS, convert a BIND 4.9 named.boot file to the BIND 8.x
named.conf format. Reload the DNS by using kill or ndc. Configure
logging in named.conf. Set the directory where zone files are located.
Includes tools and files such as:
* /etc/named.conf
* /usr/sbin/ndc
* /usr/sbin/named-bootconf
* kill
[3.1.2, 3.1.3, 3.1.6, 3.1.8, 3.1.9, 3.1.10, 3.1.14, 3.1.15]
Obj : Create and maintain DNS zones
The candidate should be able to: Create a zone file for a forward or
reverse zone, with appropriate values for the SOA resource record, NS
records and MX records. Add hosts with A resource records and CNAME
records as appropriate. Add hosts to reverse zones with PTR records.
Add the zone to the /etc/named.conf file using the zone statement with
appropriate type, file and masters values. Delegate a zone to another
DNS.
Includes tools and files such as:
* contents of /var/named
* zone file syntax
* resource record formats
[3.1.1, 3.1.4, 3.1.5, 3.1.13, 3.1.19]
Obj: Secure the DNS system
The candidate should be able to: Configure BIND to run as a non-root
user, and configure BIND to run in a chroot jail. Configure DNSSEC
statements such as key and trusted-keys to prevent domain spoofing.
Configure a split DNS configuration using the forwarders statement.
Specify a non-standard version number string in response to queries.
Includes tools and files such as:
* SysVInit files or rc.local
* /etc/named.conf
*/etc/passwd
* dnskeygen
3.1.1 Configure BIND to run as a non-root user.
3.1.2 Add a host to the primary domain databases, updating both forward and
reverse domains.
3.1.3 Remove a host from the primary domain databases, updating both forward
and reverse domains.
3.1.4 Use the key and trusted-keys statement in BIND to prevent domain
spoofing
3.1.5 Configure BIND to run in a chroot jail.
3.1.6 Add domains to the DNS server by using named.conf
3.1.7 Configure a caching-only DNS.
3.1.8 Create a primary forward domain and add it to the name server.
3.1.9 Create a primary reverse domain (in-addr.arpa domain) and add it to
the name server.
3.1.10 Configure bind to be a slave DNS server for a domain.
3.1.11 Set up a DNS server master/slave
3.1.12 Upgrading BIND 4 zone file format to BIND 8.x named.conf file format
3.1.13 Set up BIND behind a firewall for internal use only
3.1.14 Configure A, SOA, NS, CNAME, PTR, and MX type records
3.1.15 Delegate DNS (reverse and forward) for a subdomain.
3.1.16 Reload a changed configuration by using either kill or ndc
3.1.17 Configure logging with the logging statement in named.conf.
3.1.18 Specify the location of the DNS zone files.
3.1.19 Specify a spurious version number with the options statement.
3.10.1 L3 Set up a mirror server to take over if a primary server fails
