Difference between revisions of "OPS335 Assignment 1b - rev 2 - Murray Saul"

From CDOT Wiki
Jump to: navigation, search
(Evaluation Rubric)
Line 189: Line 189:
 
::'''MX''' record
 
::'''MX''' record
 
| style="text-align:right" | /1
 
| style="text-align:right" | /1
|-
 
|
 
 
|-
 
|-
 
| colspan=2 | '''Slave Name Server (spruce) - Network Configuration'''
 
| colspan=2 | '''Slave Name Server (spruce) - Network Configuration'''

Revision as of 09:41, 8 February 2017

Important.png
This is NOT Assignment 1 Part 2!
This is the ROUGH WORK for Murray Saul's section for OPS335 Assignment 1 - Part 2. These assignment specifications are NOT complete.

Once the assignment specifications are ready, then a link will appear in the Main OPS335 WIKI .


Purpose

In this assignment, you will use the 335assign virtual network and the seedling cloning-source that you created in assignment 1 (part 1) to create two name-servers. One of the cloned VMs (hostname: balsam) will be a master name server, and the other VM (hostname: spruce) will be a slave name server. You will install and setup the master and slave servers in order to provide various domain name resolutions for existing servers, and for servers that will be created and used in assignment #2.


General Requirements

Weight: 7% of the overall grade

Due Date: During Week 9 (in class)


Detailed Requirements

Set-up Master Name Server (balsam)

Perform the following steps for this section:

  1. Create a clone virtual machine called balsam from the seedling cloning-source. Refer to the table below for address and hostname.
  2. Create a regular user for this virtual machine using your Seneca userID.
  3. Setup a DNS server on your balsam virtual machine with noting the following items below:
    1. This virtual machine will be the Master DNS server.
    2. This machine will provide forward lookups of ALL virtual machines in the coniferous.trees.ops zone, including resource records for virtual machines that do not currently exist.
    3. Make certain to include an MX record for your admin e-mail contact: yoursenecaid@coniferous.trees.ops
    4. Any machine in the coniferous.trees.ops network may use this machine to perform queries of machines outside the network, however it will route all such queries through the DNS server you created in lab #3.

Set-up Slave Name Server (spruce)

Perform the following steps for this section:

  1. Create a clone virtual machine called spruce from the seedling cloning-source. Refer to the table below for address and hostname.
  2. Create a regular user for this virtual machine using your Seneca userID.
  3. Setup a DNS server on your spuce virtual machine with noting the following items below:
    1. This virtual machine will be the Slave DNS server (in case the Master Name Server goes down).
    2. This virtual machine will obtain its zone files by copying them from the Master Name Server.
    3. This Slave DNS server will check for updated records from the Master DNS server every day. If the initial attempt fails, then it will attempt every hour until it succeeds.
    4. This machine will provide forward lookups of ALL virtual machines in the coniferous.trees.ops zone, the zone files for which will be obtained from balsam.coniferous.trees.ops.
    5. Only machines within the coniferous.trees.ops domain will be allowed to query this machine.
    6. This machine will not provide recursive lookup capabilities for any machines.

Network Configuration

As you will now have functioning primary and secondary DNS servers, modify your network configuration file on these machines and on the cloning source to specify the correct IPADDR.


Table of Virtual Machines / DNS Records

All the machines in the following table require DNS records. The rows not shaded represent future servers that will be created in Assignment #2.

Hostname Address Purpose
spruce.coniferous.trees.ops (your existing source) External Facing Address: DHCP assigned
Internal Virtual Bridge (virbr1): 172.30.20.1
Your host machine
seedling.coniferous.trees.ops 172.30.20.100 Cloning-source used to create other servers for other assignments.
balsam.coniferous.trees.ops 172.30.20.2 Master Name Server
spruce.coniferous.trees.ops 172.30.20.3 Slave Name Server
pine.coniferous.trees.ops 172.30.20.5 SMTP mail Server
fir.coniferous.trees.ops 172.30.20.6 IMAP mail Server
bristlecone.coniferous.trees.ops 172.30.20.8 Samba Server

Set-up Firewall Policies

In addition to the basic firewall established in assignment 1, ensure the following restrictions are met:

  1. Any machine may query balsam
  2. Only the machines in the coniferous.trees.ops network may query spruce.
  3. Only spruce is allowed to get zone transfers from balsam

Assignment Submission

The student is required to prove to their professor that their set-up works correctly during the regularly-scheduled lab period.

Assignment Evaluation Details

  • Demonstrate working assignment to your instructor in class:
    1. Students need to demonstrate their assignment functionality to their professor during a lab period
      (like you would for any lab for "sign-off").
    2. Students are required to prepare everything ahead of time so that you can quickly demonstrate to your instructor that all required parts of your assignment are working.
    3. Do do proceed to the next step until you have demonstrated your assignment to your instructor to check for errors that may cause problems when running the checking script.

  • Download and run a shell script to check your work (Depending on your OPS335 Instructor):


Peter Callaghan's Classes (Sections C & D):
  • Refer to instruction on Moodle to download and run marking shell script.


Murray Saul's Classes (Sections A & B):
  1. Login as root on your host machine.
  2. Change to the /root/bin directory.
  3. Make certain that both your balsam and spruce virtual machines are running.
  4. Issue the command to download a checking script for your assignment to your host machine:
    wget http://matrix.senecac.on.ca/~murray.saul/ops335/check-assn1-p2.bash
  5. Set execute permissions and run the command: /root/bin/check-assn1-p2.bash
    (You shell script contents will be mailed to your Seneca email and to your OPS335 instructor's Seneca email. If you do NOT receive an e-mail message in your Seneca email account, then there is a problem, and you MUST rerun or contact your OPS335 instructor immediately.

  • Additional Assignment Information:
    1. This assignment is to be completed individually. Group submissions are not allowed.
    2. You are NOT allowed to use local hostname resolution (i.e. no entries in your /etc/hosts file).
    3. Test your machine to make sure it works. If a machine is not accessible (e.g. will not boot, can not be accessed through ssh from your host, etc.), or is otherwise non-functional, you may be told to resubmit.
    4. Late submissions are a subject to a penalty of 10% per day.

    Evaluation Rubric

    Here is an evaluation rubric (in table form) showing you how you will be evaluated for this assignment. Part of the rubric is marked from professor observation from student demonstration of assignment in class, and the other part is based on output from the results of an assignment checking script that the student will download and run.

    Student Demonstration (in class)
    Evaluation Item Mark
    balsam and spruce VMs created
    /1
    balsam and spruce VMs can connect to Internet
    /1
    balsam and spruce VMs can perform DNS queries for vm1, vm2, vm3
    /1
    balsam and spruce VMs can perform DNS queries outside Seneca Network
    /1
    balsam and spruce VMs can perform forward DNS lookups for ALL machines within network (listed in the table above)
    /1
    Configuration (Checking Script Output)
    Evaluation Item Mark
    Master Name Server (balsam) - Network Configuration
    Domain set
    /1
    Has correct ip addresses
    /1
    Default gateway set
    /1
    DNS1 set
    /1
    DNS2 set
    /1
    Master Name Server (balsam) - Named Configuration Options / Zone Declarations
    Zone transfer (i.e. to slave DNS server) limited to spruce only
    /1
    Allows forward lookup to coniferous.trees.ops
    /1
    Allows forward lookup to vm1
    /1
    Recursion limited to coniferous.trees.ops only
    /1
    balsam server is the master name-server for coniferous.trees.ops
    /1
    Master Name Server (balsam) - Zone Record
    SOA - Refresh timer set
    /1
    SOA - Retry timer set
    /1
    NS records in forward zone
    /1
    A records (existing vms balsam and spruce as well as vms to be created later)
    /5
    MX record
    /1
    Slave Name Server (spruce) - Network Configuration
    Domain set
    /1
    Has correct ip addresses
    /1
    Default gateway set
    /1
    DNS1 set
    /1
    DNS2 set
    /1
    Slave Name Server (spuce) - Named Configuration Options
    Queries are limited to coniferous.trees.ops
    /1
    Slave server is Non-recursive
    /1
    Allows forward lookup for coniferous.trees.ops
    /1
    spruce server is slave name-server for coniferous.trees.ops
    /1
    Firewall policies
    iptables NOT blocking queries
    /1
    iptables limiting queries to coniferous.trees.ops (won't work with vm1, vm2, vm3)
    /1
    Less Deductions (half-mark for EACH VM):
    • SELinux NOT Enforcing
    • VM hostname NOT set
    • firewalld enabled / running
    • iptables disabled / not running
    • No Yum update
    • Named NOT active
    • local hostname resolution still remaining in /etc/hosts
    TOTAL /35