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

From CDOT Wiki
Jump to: navigation, search
 
(189 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
{{Admon/important|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. <br><br>Once the assignment specifications are ready, then a link will appear in the [https://wiki.cdot.senecacollege.ca/wiki/OPS335 Main OPS335 WIKI] .}}<br><br>
 +
 
== Purpose ==
 
== Purpose ==
  
In this assignment, you will use the newer virtual network (335assign) and the cloning-source that you created in previous assignment (lab1a) to create 2 name-servers. One of the name servers will be the master, and the other one a secondary (slave) name server. You will configure the master name server to provide various domain name resolutions for existing servers, and for servers that will be created and used in assignment #2.
+
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 ==
 
== General Requirements ==
  
'''Weight''': 5% of the overall grade
+
'''Weight''': 7% of the overall grade
  
 
'''Due Date''': During Week 9 (in class)
 
'''Due Date''': During Week 9 (in class)
Line 13: Line 16:
  
  
=== Virtual Network ===
+
=== Set-up Master Name Server ('''balsam''')===
 +
 
 +
Perform the following steps for this section:
 +
 
 +
#Create a clone virtual machine called '''balsam''' from the '''seedling''' cloning-source. Refer to the table below for '''address''' and '''hostname'''.
 +
#Create a '''regular user''' for this virtual machine using '''your Seneca userID'''.
 +
#Setup a DNS server on your '''balsam''' virtual machine with noting the following items below:<ol type="a"><li>This virtual machine will be the '''Master DNS server'''.</li><li>This machine will provide '''forward''' and '''reverse''' lookups of ALL virtual machines in the '''coniferous.trees.ops''' zone, including resource records for virtual machines that do not currently exist.</li><li> Make certain to include an '''MX record''' for your admin e-mail contact: '''yoursenecaid@coniferous.trees.ops'''</li><li>This machine will allow other machines (outside the '''coniferous.trees.ops.''' zone) to perform DNS lookups among ALL virtual machines within the '''coniferous.trees.ops''' network.</li><li>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.</li></ol>
 +
 
 +
=== Set-up Slave Name Server ('''spruce''') ===
 +
 
 +
Perform the following steps for this section:
 +
 
 +
#Create a clone virtual machine called '''spruce''' from the '''seedling''' cloning-source. Refer to the table below for '''address''' and '''hostname'''.
 +
#Create a '''regular user''' for this virtual machine using '''your Seneca userID'''.
 +
#Setup a DNS server on your '''spuce''' virtual machine with noting the following items below:<ol type="a"><li>This virtual machine will be the '''Slave DNS server''' (in case the Master Name Server goes down).</li><li>This virtual machine will obtain its zone files by copying them from the Master Name Server.</li><li>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.</li><li>This machine will provide '''forward''' and '''reverse''' lookups of ALL virtual machines in the '''coniferous.trees.ops''' zone, the zone files for which will be obtained from '''balsam.coniferous.trees.ops'''.</li><li>Only machines within the '''coniferous.trees.ops''' domain will be allowed to query this machine.</li><li>This machine will not provide recursive lookup capabilities for any machines.<br><br></li></ol>
 +
 
 +
=== Network Configuration ===
  
Create a new virtual network on your Host Machine.
+
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.
  
* Assign a newly-created virtual network the name: '''asg1net''', and set '''forwarding to any physical device'''<br>(refer to [http://zenit.senecac.on.ca/wiki/index.php/OPS335_Installation_Lab#INVESTIGATION_2:_VIRTUAL_MACHINE_INSTALLATION lab setup]. You can have have 2 different network names: "asg1net"  and "ops335" without causing any problems).
 
* Addresses in this network will start with '''10.161''' followed by the '''last two digits of your student number''' (just as your main virtual network). The subnet mask must be '''255.255.255.0'''
 
* There must '''<u>NOT</u>''' be a DHCP server running for this network!
 
* All the machines for this assignment will be connected to your newly-created virtual network called: '''asg1net'''
 
  
 +
=== Table of Virtual Machines / DNS Records ===
  
=== Create a "Cloning Source" VM (asg1net Virtual Network) ===
+
'''All''' the machines in the following table require DNS records. The rows not shaded represent future servers that will be created in Assignment #2.
  
Create a virtual machine that you will use as a template (i.e. a '''cloning source'''). It should have a command-line interface only. Configure it to be a good cloning source, making certain it has all the following elements prior to cloning:
+
{| class="wikitable" | style="margin-left:0px;"
 +
! Hostname !! Address !! Purpose
 +
|-style="background-color:#66cccc;"
 +
| '''spruce.coniferous.trees.ops''' (your existing source) ||  External Facing Address:''' DHCP assigned'''<br>Internal Virtual Bridge (virbr1):''' 172.30.20.1''' || Your '''host''' machine
  
# Don't make the virtual drive too big: you will need space for it as well as space for the clones you from your cloning source<br>(2GB should be enough for any cloning source and clone VM that you create for this assignment).
+
|-style="background-color:#66cccc;"
# Make certain that you can login to your cloning source. The minimum commands required are: '''host''', '''dig''', '''netstat''', '''links'''.
+
| '''seedling.coniferous.trees.ops''' || '''172.30.20.100''' || '''Cloning-source''' used to create other servers for other assignments.
# Do not install software on your cloning source: you are expected to install other software on your "cloned" VMs instead. For example, if you are required to install bind in a clone, install it in the clone as opposed to the "cloning source".
+
|-style="background-color:#66cccc;"
# Configure your network with a static configuration. Refer to the table below for IP address and hostname.
+
| '''balsam.coniferous.trees.ops''' || ''' 172.30.20.2''' || '''Master''' Name Server
# Make certain that you have '''iptables''' services enabled and running instead of ''Firewalld''. The default rules should suffice.
 
# If you have created a regular user when you installed the machine, delete that regular user (you are to use only the root account).
 
# Set up an SSH server on this "cloning source". Make sure that the root account is only permitted to log in using key authentication. If user users are required to be created later, they should be permitted to log in with a their username and password.
 
# Generate a new key pair on your Host Machine (don't delete the existing one), called: '''id_rsa_asg1'''
 
# Make sure you can log in from your regular user on your Host Machine to root on the "cloning source" virtual machine using specifically that key.
 
# Do not place that newly-generated private key on the "cloning source" VM.
 
  
 +
|-style="background-color:#66cccc;"
 +
| '''spruce.coniferous.trees.ops''' || '''172.30.20.3'''  || '''Slave''' Name Server
 +
|-  style="background-color:white;"
 +
| '''pine.coniferous.trees.ops''' || ''' 172.30.20.5''' || '''SMTP''' mail Server
  
=== Clone "ns1" VM from "Cloning Source" &amp; Perform Setup Tasks===
+
|-  style="background-color:white;"
 +
| '''fir.coniferous.trees.ops''' || '''172.30.20.6'''  || '''IMAP''' mail Server
 +
|-  style="background-color:white;"
 +
|'''bristlecone.coniferous.trees.ops''' || '''172.30.20.8'''  || '''Samba''' Server
 +
|}
  
Perform the following steps for this section:
+
===Set-up Firewall Policies===
 +
 
 +
In addition to the basic firewall established in assignment 1, ensure the following restrictions are met:
 +
 
 +
# Any machine may query '''balsam'''
 +
# Only the machines in the '''coniferous.trees.ops''' network may query spruce.
 +
# 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===
  
#Create a clone called: '''ns1''' from the "cloning source" that will act as your '''master DNS server''' on the '''asg1net''' network. Refer to the table below for address and hostname.
+
*'''Demonstrate working assignment to your instructor in class:'''<ol type="a"><li>Students need to demonstrate their assignment functionality to their professor during a lab period<br>(like you would for any lab for "sign-off").</li><li>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.</li><li>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.<br><br></li></ol>
#Make certain that your DNS server must has all the records for the zone called: '''ops335a1.org''' listed in that table, including records for machines that do not exist as of yet. It is important to understand that DNS records live independently from the machines that they are "pointing" to.
 
#A default setup for a master DNS server should be sufficient, but make certain that the address of your '''admin contact''' is: '''yoursenecaid@ops335a1.org''', and that slave DNS servers will check for updated records from this master every 30 minutes.
 
  
 +
*Download and run a shell script to check your work (Depending on your OPS335 Instructor):
  
=== Clone "ns2" VM from "Cloning Source" &amp; Perform Setup Tasks ===
 
  
Perform the following steps for this section:
+
::'''Peter Callaghan's Classes (Sections C &amp; D):'''<ul><li>Refer to instruction on Moodle to download and run marking shell script.</li></ul>
  
#Create a clone called '''ns2''' from the cloning source that will act as your '''slave DNS server''' on the '''asg1net''' network. Refer to the table below for address and hostname.
 
#The '''ns2''' machine will serve the same records as '''ns1'''.
 
  
 +
::'''Murray Saul's Classes (Sections A &amp; B):'''<ol><li>Login as '''root''' on your '''host''' machine.</li><li>Change to the '''/root/bin''' directory.</li><li>Make certain that both your '''balsam''' and '''spruce''' virtual machines are running.<li>Issue the command to download a checking script for your assignment to your '''host''' machine: <source>wget http://matrix.senecac.on.ca/~murray.saul/ops335/check-assn1-p2.bash</source></li><li>Set execute permissions and run the command: '''/root/bin/check-assn1-p2.bash'''<br>(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.<br><br></li></ol>
 +
*'''Additional Assignment Information:'''<ol type="a"><li>This assignment is to be completed individually. '''Group submissions are not allowed'''.</li><li>You are NOT allowed to use local hostname resolution (i.e. no entries in your '''/etc/hosts''' file).<li>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'''.</li><li>'''Late submissions are a subject to a penalty of 10% per day'''.</li><ol>
  
=== Reference Materials: List of Machines / DNS Records ===
+
==Evaluation Rubric==
  
All the machines in the table need DNS records, but only the ones in bold need to be existing machines for this assignment.
+
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.
  
{| class="wikitable"
+
{| class="wikitable" width=60%
! Name !! Address !! Purpose
+
|-
 +
| colspan=2 style="text-align:center;background-color:#cccccc;" |'''Student Demonstration (in class)'''
 +
|-
 +
| style="font-weight:bold" | Evaluation Item
 +
| width=10% style="text-align:right;font-weight:bold" | Mark
 +
|-
 +
|
 +
::'''balsam''' and '''spruce''' VMs created
 +
| style="text-align:right" | /1
 +
|-
 +
|
 +
::'''balsam''' and '''spruce''' VMs can connect to Internet
 +
| style="text-align:right" | /1
 +
|-
 +
|
 +
::'''balsam''' and '''spruce''' VMs can perform '''DNS queries outside network'''
 +
| style="text-align:right" | /1
 +
|-
 +
|
 +
::'''balsam''' and '''spruce''' VMs can perform '''forward DNS lookups''' for ALL machines within network
 +
| style="text-align:right" | /1
 +
|-
 +
|
 +
::'''balsam''' and '''spruce''' VMs can perform '''reverse DNS lookups''' for ALL machines within network
 +
| style="text-align:right" | /1
 +
|-
 +
| colspan=2 style="text-align:center;background-color:#cccccc;" |'''Configuration (Checking Script Output)'''
 +
|-
 +
| style="font-weight:bold;" | Evaluation Item
 +
| width=10% style="text-align:right;font-weight:bold" | Mark
 
|-
 
|-
| '''host.ops335a1.org''' || 10.161.X.1 || Your host machine
+
|  colspan=2 | '''Master Name Server (balsam) - General Configuration'''
 
|-
 
|-
| '''ns1.ops335a1.org''' || 10.161.X.2 || Master name server
+
|  
 +
::Domain set
 +
| style="text-align:right" | /1
 
|-
 
|-
| '''ns2.ops335a1.org''' || 10.161.X.3 || Slave name server
+
|  
 +
::Has correct ip addresses
 +
| style="text-align:right" | /1
 
|-
 
|-
| file.ops335a1.org || 10.161.X.4 || File server
+
|  
 +
::Default gateway set
 +
| style="text-align:right" | /1
 
|-
 
|-
| www.ops335a1.org || 10.161.X.5 || Web server
+
|  
 +
::DNS1 set
 +
| style="text-align:right" | /1
 
|-
 
|-
| '''source.ops335a1.org''' || 10.161.X.254 || Disk image to clone from when creating new machines.
+
|  
 +
::DNS2 set
 +
| style="text-align:right" | /1
 +
|-
 +
|  colspan=2 | '''Master Name Server (balsam) - Named Configuration'''
 +
|-
 +
|
 +
::Zone transfer (to slave DNS server) limited to spruce only
 +
| style="text-align:right" | /2
 +
|-
 +
|
 +
::Forwards to VM1
 +
| style="text-align:right" | /2
 +
|-
 +
|
 +
::Recursion limited to coniferous
 +
| style="text-align:right" | /2
 +
|-
 +
|
 +
::coniferous.trees.ops forward lookup
 +
| style="text-align:right" | /3
 +
|-
 +
|
 +
::Server is master for coniferous.trees.ops
 +
| style="text-align:right" | /2
 +
|-
 +
|
 +
::NS records in forward zone
 +
| style="text-align:right" | /1
 +
|-
 +
|
 +
::No extra NS records
 +
| style="text-align:right" | /1
 +
|-
 +
|
 +
::Refresh timer set
 +
| style="text-align:right" | /1
 +
|-
 +
|
 +
::Retry timer set
 +
| style="text-align:right" | /1
 +
|-
 +
|
 +
::A records
 +
| style="text-align:right" | /3
 +
|-
 +
|
 +
::spiral.galaxies.ops reverse lookup
 +
| style="text-align:right" | /3
 +
|-
 +
|
 +
::Server is master for 172.30.20
 +
| style="text-align:right" | /1
 +
|-
 +
|
 +
::NS records in 20.30.172
 +
| style="text-align:right" | /2
 +
|-
 +
|
 +
::No extra NS records
 +
| style="text-align:right" | /1
 +
|-
 +
|
 +
::PTR records
 +
| style="text-align:right" | /3
 +
|-
 +
|
 +
::Hierarchy to sub-domain
 +
| style="text-align:right" | /3
 +
 
 +
|-
 +
| colspan=2 | '''Slave Name Server (spruce) - General Configuration'''
 +
|-
 +
|
 +
::Domain set
 +
| style="text-align:right" | /1
 +
|-
 +
|
 +
::Has correct ip addresses
 +
| style="text-align:right" | /1
 +
|-
 +
|
 +
::Default gateway set
 +
| style="text-align:right" | /1
 +
|-
 +
|
 +
::DNS1 set
 +
| style="text-align:right" | /1
 +
|-
 +
|
 +
::DNS2 set
 +
| style="text-align:right" | /1
 +
|-
 +
|  colspan=2 | '''Slave Name Server (spuce) - Named Configuration'''
 +
|-
 +
|
 +
::Queries limited to coniferous.trees.ops
 +
| style="text-align:right" | /2
 +
|-
 +
|
 +
::Non-recursive
 +
| style="text-align:right" | /1
 +
|-
 +
|
 +
::coniferous.trees.ops forward lookup
 +
| style="text-align:right" | /3
 +
|-
 +
|
 +
::Server is slave for coniferous.trees.ops
 +
| style="text-align:right" | /1
 +
|-
 +
|
 +
::Master for coniferous.trees.ops set
 +
| style="text-align:right" | /1
 +
|-
 +
|
 +
::coniferous.trees.ops reverse lookup
 +
| style="text-align:right" | /3
 +
|-
 +
|  
 +
::Server is slave for 172.30.20
 +
| style="text-align:right" | /1
 +
|-
 +
|
 +
::Master for 172.30.20 set
 +
| style="text-align:right" | /1
 +
|-
 +
|
 +
::Zone transfer works
 +
| style="text-align:right" | /4
 +
|-
 +
| colspan=2 | '''Firewall policies'''
 +
|-
 +
|
 +
::queries allowed
 +
| style="text-align:right" | /2
 +
|-
 +
|
 +
::queries limited to coniferous
 +
| style="text-align:right" | /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</li><li>Named NOT active
 +
:*local hostname resolution remaining in '''/etc/hosts'''
 +
|
 +
|-
 +
| '''TOTAL'''
 +
| style="text-align:right" | '''/64'''
 
|}
 
|}
  
 
+
[https://wiki.cdot.senecacollege.ca/wiki/OPS335_Assignment_2_-_Murray_Saul_rev1 assn2]
== Assignment Submission ==
 
 
 
Submit the following in Blackboard, Moodle, or whatever your professor specifies in class or "class announements" (For Murray Saul, also send these in an e-mail (subject line: OPS335 assignment1) with the following attachments):
 
 
 
# '''Screenshots''' to demonstrate you have accomplished the required tasks for this assignment.<br>This includes: '''configuration files''', '''service statuses''', and '''basic tests of functionality'''.''' NOTE: You MUST take screenshoots of the ENTIRE screen as opposed to only the VM console'''.
 
# Your '''test plan''' in '''PDF''' format.
 
 
 
*Demonstrate working assignment to your instructor in class:
 
**Also you need to show your assignment to the professor in a lab period (like you would for any lab for "sign-off"). This requires you to prepare everything ahead of time so that you can quickly demonstrate to your instructor that all required parts of your assignment are working.
 

Latest revision as of 15:30, 28 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 and reverse 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. This machine will allow other machines (outside the coniferous.trees.ops. zone) to perform DNS lookups among ALL virtual machines within the coniferous.trees.ops network.
    5. 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 and reverse 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 outside network
    /1
    balsam and spruce VMs can perform forward DNS lookups for ALL machines within network
    /1
    balsam and spruce VMs can perform reverse DNS lookups for ALL machines within network
    /1
    Configuration (Checking Script Output)
    Evaluation Item Mark
    Master Name Server (balsam) - General 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
    Zone transfer (to slave DNS server) limited to spruce only
    /2
    Forwards to VM1
    /2
    Recursion limited to coniferous
    /2
    coniferous.trees.ops forward lookup
    /3
    Server is master for coniferous.trees.ops
    /2
    NS records in forward zone
    /1
    No extra NS records
    /1
    Refresh timer set
    /1
    Retry timer set
    /1
    A records
    /3
    spiral.galaxies.ops reverse lookup
    /3
    Server is master for 172.30.20
    /1
    NS records in 20.30.172
    /2
    No extra NS records
    /1
    PTR records
    /3
    Hierarchy to sub-domain
    /3
    Slave Name Server (spruce) - General 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
    Queries limited to coniferous.trees.ops
    /2
    Non-recursive
    /1
    coniferous.trees.ops forward lookup
    /3
    Server is slave for coniferous.trees.ops
    /1
    Master for coniferous.trees.ops set
    /1
    coniferous.trees.ops reverse lookup
    /3
    Server is slave for 172.30.20
    /1
    Master for 172.30.20 set
    /1
    Zone transfer works
    /4
    Firewall policies
    queries allowed
    /2
    queries limited to coniferous
    /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 remaining in /etc/hosts
    TOTAL /64
    assn2