Difference between revisions of "OPS335 - Assignment 1 (Part 2)"
Line 1: | Line 1: | ||
== Purpose == | == Purpose == | ||
− | In this assignment, you will use the '''335assign''' virtual network and the '''minnow''' cloning-source that you created in assignment 1 (part 1) to create two name-servers. One of the cloned VMs (hostname: '''pike''') will be a '''master''' name server, and the other VM (hostname: ''' | + | In this assignment, you will use the '''335assign''' virtual network and the '''minnow''' cloning-source that you created in assignment 1 (part 1) to create two name-servers. One of the cloned VMs (hostname: '''pike''') will be a '''master''' name server, and the other VM (hostname: '''pickerel''') 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 == | ||
Line 18: | Line 18: | ||
#Create a clone virtual machine called '''pike''' from the '''minnow''' cloning-source. Refer to the table below for '''address''' and '''hostname'''. | #Create a clone virtual machine called '''pike''' from the '''minnow''' cloning-source. Refer to the table below for '''address''' and '''hostname'''. | ||
#Create a '''regular user''' for this virtual machine using '''your Seneca userID'''. | #Create a '''regular user''' for this virtual machine using '''your Seneca userID'''. | ||
− | #Setup a DNS server on your '''pike''' virtual machine noting the following items below:<ol type="a"><li>This virtual machine will be the '''Master DNS server''' for '''species.lake.ops'''.</li><li>Only ''' | + | #Setup a DNS server on your '''pike''' virtual machine noting the following items below:<ol type="a"><li>This virtual machine will be the '''Master DNS server''' for '''species.lake.ops'''.</li><li>Only '''pickerel''' will be allowed to obtain zone transfers of this zone.</li><li>This machine will provide '''forward''' and '''reverse''' lookups of ALL virtual machines in the '''species.lake.ops.''' zone, including resource records for virtual machines that do not currently exist.</li><li> Include an '''MX record''' for email sent to the domain to be directed to '''jaguar.species.lake.ops'''.</li><li>Any machine in the '''species.lake.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><li>For machines outside the '''species.lake.ops''' domain, it will only answer queries about machines inside the network. They may not use it to query other machines.</li></ol> |
− | === Set-up Slave Name Server (''' | + | === Set-up Slave Name Server ('''pickerel''') === |
Perform the following steps for this section: | Perform the following steps for this section: | ||
− | #Create a clone virtual machine called ''' | + | #Create a clone virtual machine called '''pickerel''' from the '''minnow''' cloning-source. Refer to the table below for '''address''' and '''hostname'''. |
#Create a '''regular user''' for this virtual machine using '''your Seneca userID'''. | #Create a '''regular user''' for this virtual machine using '''your Seneca userID'''. | ||
− | #Setup a DNS server on your ''' | + | #Setup a DNS server on your '''pickerel''' virtual machine 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 two days. If the initial attempt fails, then it will attempt every six hours until it succeeds, or one week has passed.</li><li>This machine will provide '''forward''' and '''reverse''' lookups of ALL virtual machines in the '''species.lake.ops''' zone, the zone files for which will be obtained from '''pike.species.lake.ops'''.</li><li>Only machines within the '''species.lake.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 === | === Network Configuration === | ||
Line 56: | Line 56: | ||
|-style="background-color:#66cccc; border: 2px solid black;" | |-style="background-color:#66cccc; border: 2px solid black;" | ||
− | | style="background-color:#66cccc; border: 2px solid black;" | ''' | + | | style="background-color:#66cccc; border: 2px solid black;" | '''pickerel.species.lake.ops''' |
| style="background-color:#66cccc; border: 2px solid black;" | '''172.45.20.4''' | | style="background-color:#66cccc; border: 2px solid black;" | '''172.45.20.4''' | ||
| style="background-color:#66cccc; border: 2px solid black;" | '''Slave''' Name Server | | style="background-color:#66cccc; border: 2px solid black;" | '''Slave''' Name Server | ||
Line 79: | Line 79: | ||
# Any machine may query '''pike''' | # Any machine may query '''pike''' | ||
− | # Only the machines in the '''species.lake.ops''' network may query | + | # Only the machines in the '''species.lake.ops''' network may query pickerel. |
== Assignment Submission == | == Assignment Submission == | ||
Line 115: | Line 115: | ||
|- | |- | ||
| | | | ||
− | ::'''pike''' and ''' | + | ::'''pike''' and '''pickerel''' VMs created |
| style="text-align:right" | /1 | | style="text-align:right" | /1 | ||
|- | |- | ||
| | | | ||
− | ::'''pike''' and ''' | + | ::'''pike''' and '''pickerel''' VMs can perform '''DNS queries of vm1, vm2, vm3''' |
| style="text-align:right" | /1 | | style="text-align:right" | /1 | ||
|- | |- | ||
| | | | ||
− | ::'''pike''' and ''' | + | ::'''pike''' and '''pickerel''' VMs can perform '''forward DNS lookups''' for ALL machines within network (listed in the table above) |
| style="text-align:right" | /3 | | style="text-align:right" | /3 | ||
|- | |- | ||
| | | | ||
− | ::'''pike''' and ''' | + | ::'''pike''' and '''pickerel''' VMs can perform '''reverse DNS lookups''' for ALL machines within network (listed in the table above) |
| style="text-align:right" | /3 | | style="text-align:right" | /3 | ||
|- | |- | ||
Line 148: | Line 148: | ||
|- | |- | ||
| | | | ||
− | ::Zone transfer (i.e. to slave DNS server) limited to ''' | + | ::Zone transfer (i.e. to slave DNS server) limited to '''pickerel''' only |
| style="text-align:right" | /1 | | style="text-align:right" | /1 | ||
|- | |- | ||
Line 181: | Line 181: | ||
| style="text-align:right" | /1 | | style="text-align:right" | /1 | ||
|- | |- | ||
− | | colspan=2 style="background-color:#eeeeee;"| '''Slave Name Server ( | + | | colspan=2 style="background-color:#eeeeee;"| '''Slave Name Server (pickerel) - Network Configuration''' |
|- | |- | ||
| | | | ||
Line 187: | Line 187: | ||
| style="text-align:right" | /5 | | style="text-align:right" | /5 | ||
|- | |- | ||
− | | colspan=2 style="background-color:#eeeeee;"| '''Slave Name Server ( | + | | colspan=2 style="background-color:#eeeeee;"| '''Slave Name Server (pickerel) - Named Configuration Options''' |
|- | |- | ||
| | | | ||
Line 202: | Line 202: | ||
|- | |- | ||
| | | | ||
− | :: | + | ::pickerel server is '''slave''' name-server for '''species.lake.ops''' |
| style="text-align:right" | /1 | | style="text-align:right" | /1 | ||
|- | |- | ||
Line 212: | Line 212: | ||
|- | |- | ||
| | | | ||
− | ::''' | + | ::'''pickerel''' limits queries to '''species.lake.ops''' (i.e. won't work with '''vm1''', '''vm2''', '''vm3''') |
| style="text-align:right" | /2 | | style="text-align:right" | /2 | ||
|- | |- |
Revision as of 15:53, 11 May 2018
Contents
Purpose
In this assignment, you will use the 335assign virtual network and the minnow cloning-source that you created in assignment 1 (part 1) to create two name-servers. One of the cloned VMs (hostname: pike) will be a master name server, and the other VM (hostname: pickerel) 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 (pike)
Perform the following steps for this section:
- Create a clone virtual machine called pike from the minnow 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 pike virtual machine noting the following items below:
- This virtual machine will be the Master DNS server for species.lake.ops.
- Only pickerel will be allowed to obtain zone transfers of this zone.
- This machine will provide forward and reverse lookups of ALL virtual machines in the species.lake.ops. zone, including resource records for virtual machines that do not currently exist.
- Include an MX record for email sent to the domain to be directed to jaguar.species.lake.ops.
- Any machine in the species.lake.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.
- For machines outside the species.lake.ops domain, it will only answer queries about machines inside the network. They may not use it to query other machines.
Set-up Slave Name Server (pickerel)
Perform the following steps for this section:
- Create a clone virtual machine called pickerel from the minnow 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 pickerel virtual machine noting the following items below:
- This virtual machine will be the Slave DNS server (in case the Master Name Server goes down).
- This virtual machine will obtain its zone files by copying them from the Master Name Server.
- This Slave DNS server will check for updated records from the Master DNS server every two days. If the initial attempt fails, then it will attempt every six hours until it succeeds, or one week has passed.
- This machine will provide forward and reverse lookups of ALL virtual machines in the species.lake.ops zone, the zone files for which will be obtained from pike.species.lake.ops.
- Only machines within the species.lake.ops domain will be allowed to query this machine.
- 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 / Domain | Address | Purpose |
freshwater.species.lake.ops (your existing host) | External Facing Address: DHCP assigned Internal Virtual Bridge (virbr1): 172.45.20.1 |
Your host machine |
minnow.species.lake.ops | 172.45.20.100 | Cloning-source used to create other servers for other assignments. |
pike.species.lake.ops | 172.45.20.3 | Master Name Server |
pickerel.species.lake.ops | 172.45.20.4 | Slave Name Server |
jaguar.species.lake.ops | 172.45.20.7 | SMTP mail Server |
bmw.species.lake.ops | 172.45.20.8 | IMAP mail Server |
volvo.species.lake.ops | 172.45.20.9 | Samba Server |
Set-up Firewall Policies
In addition to the basic firewall established in assignment 1, ensure the following restrictions are met:
- Any machine may query pike
- Only the machines in the species.lake.ops network may query pickerel.
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:
- You need to run their full backup shell script to backup all of your VMs (like you did in Assignment 1 - Part 1.
- Students need to demonstrate their assignment functionality to their professor during a lab period
(like you would for any lab for "sign-off"). - 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.
- Do not 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 (Section D):
- Refer to instruction on blackboard for instructions on how to submit this assignment.
- Peter Callaghan's Classes (Section D):
- Colin Yip (Sections A , B & C):
- Login as root on your host machine.
- Change to the /root/bin directory.
- Make certain that your cloning-source, primary DNS and secondary VMs are running.
- Make certain that the mailx command has been installed. If not, issue the following command to install e-mail on your host machine:
yum install mailx
- Issue the command to download a checking script for your assignment to your host machine:
TBA
Set execute permissions and run the command: /root/bin/check-assn1-p2.bash
(Your 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.
- Colin Yip (Sections A , B & C):
- Additional Assignment Information:
- This assignment is to be completed individually. Group submissions are not allowed.
- 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.
- Late submissions are a subject to a penalty of 10% per day.
- Additional Assignment Information:
- This assignment is to be completed individually. Group submissions are not allowed.
- You are NOT allowed to use local hostname resolution (i.e. no entries in your /etc/hosts file).
- 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.
- Late submissions are a subject to a penalty of 10% per day.
- SELinux must be set to Enforcing.
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 |
|
/1 |
|
/1 |
|
/3 |
|
/3 |
|
/3 |
Configuration (Checking Script Output) | |
Evaluation Item | Mark |
Master Name Server (pike) - Network Configuration | |
|
/5 |
Master Name Server (pike) - Named Configuration Options / Zone Declarations | |
|
/1 |
|
/1 |
|
/1 |
|
/1 |
Master Name Server (pike) - Zone Record | |
|
/2 |
|
/2 |
|
/2 |
|
/1 |
Slave Name Server (pickerel) - Network Configuration | |
|
/5 |
Slave Name Server (pickerel) - Named Configuration Options | |
|
/1 |
|
/1 |
|
/1 |
|
/1 |
Firewall policies | |
|
/2 |
|
/2 |
Less Deductions (1 mark per issue for EACH VM): | |
|
|
TOTAL | /40 |