OPS335 Assignment 1b - Murray Saul

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: elm) will be a master name server, and the other VM (hostname: birch) 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 (elm)

Perform the following steps for this section:

1. 1. Create a clone virtual machine called elm 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 elm 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, but will exist when you perform your assignment #2.
   3. Make certain to include an MX record for your admin e-mail contact: yoursenecaid@coniferous.trees.ops
   4. For any query for information outside the coniferous.trees.ops domain, that machine will send the query to the DNS server you created in your lab #1.
   5. This machine will allow other machines to perform DNS lookups among ALL virtual machines within the coniferous.trees.ops network (i.e. recursive lookups).
   6. Only this Master Name Server will be allowed to transfer zone files from this machine.
      
      
4. As you will now have a functioning primary DNS server, modify your network configuration file to specify its new IPADDR.

Set-up slave Name Server (birch)

Perform the following steps for this section:

1. Create a clone virtual machine called birch 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 elm 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 elm.x.
   5. Make certain to include an MX record for your admin e-mail contact: yoursenecaid@coniferous.trees.ops
   6. For any query for information outside the coniferous.trees.ops domain, that machine will send the query to the DNS server you created in your lab #1.
   7. This machine will allow other machines to perform DNS lookups among ALL virtual machines within the coniferous.trees.ops network (i.e. recursive lookups).
   8. Only this Master Name Server will be allowed to transfer zone files from this machine.
      
      
4. As you will now have a functioning primary DNS server, modify your network configuration file to specify its new IPADDR.

1. 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

Reference Materials: List of Machines / DNS Records

All the machines in the table need DNS records, but only the ones in bold need to be existing machines for this assignment.

Name	Address	Purpose
host.ops335a1.org	10.161.X.1	Your host machine
ns1.ops335a1.org	10.161.X.2	Master name server
ns2.ops335a1.org	10.161.X.3	Slave name server
file.ops335a1.org	10.161.X.4	File server
www.ops335a1.org	10.161.X.5	Web server
source.ops335a1.org	10.161.X.254	Disk image to clone from when creating new machines.

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):

1. Screenshots to demonstrate you have accomplished the required tasks for this assignment.
   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.
2. 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.