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

From CDOT Wiki
Jump to: navigation, search
Line 22: Line 22:
 
#Setup a DNS server on your '''elm''' 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, but will exist when you perform your assignment #2.</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 to perform DNS lookups among ALL virtual machines within the '''coniferous.trees.ops''' network (i.e. recursive lookups).</li><li>Only this Master Name Server will be allowed to transfer zone files from this machine.<br><br></li></ol>
 
#Setup a DNS server on your '''elm''' 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, but will exist when you perform your assignment #2.</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 to perform DNS lookups among ALL virtual machines within the '''coniferous.trees.ops''' network (i.e. recursive lookups).</li><li>Only this Master Name Server will be allowed to transfer zone files from this machine.<br><br></li></ol>
 
#As you will now have a functioning primary DNS server, modify your network configuration file to specify its new IPADDR.
 
#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) ===
 
=== Set-up slave Name Server (birch) ===
Line 31: Line 32:
 
#Setup a DNS server on your '''elm''' 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 '''elm.coniferous.trees.ops'''.</li><li>Only machines within the spiral.galaxies.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>
 
#Setup a DNS server on your '''elm''' 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 '''elm.coniferous.trees.ops'''.</li><li>Only machines within the spiral.galaxies.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>
 
#As you will now have a functioning secondary DNS server, modify your network configuration file to specify its new IPADDR. You will also have to add another IPADDR for your DNS server you setup in lab #1 to allow DNS queries from your virtual machines to outside server (TIP: You cannot use your '''primary''' or '''secondary''' DNS option).
 
#As you will now have a functioning secondary DNS server, modify your network configuration file to specify its new IPADDR. You will also have to add another IPADDR for your DNS server you setup in lab #1 to allow DNS queries from your virtual machines to outside server (TIP: You cannot use your '''primary''' or '''secondary''' DNS option).
 +
  
 
=== Reference Materials: List of Machines / DNS Records ===
 
=== Reference Materials: List of Machines / DNS Records ===

Revision as of 09:52, 29 January 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: 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. 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. This machine will allow other machines to perform DNS lookups among ALL virtual machines within the coniferous.trees.ops network (i.e. recursive lookups).
    5. 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.coniferous.trees.ops.
    5. Only machines within the spiral.galaxies.ops domain will be allowed to query this machine.
    6. This machine will not provide recursive lookup capabilities for any machines.

  4. As you will now have a functioning secondary DNS server, modify your network configuration file to specify its new IPADDR. You will also have to add another IPADDR for your DNS server you setup in lab #1 to allow DNS queries from your virtual machines to outside server (TIP: You cannot use your primary or secondary DNS option).


Reference Materials: List of Machines / DNS Records

All the machines in the table need 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.
elm.coniferous.trees.ops 172.30.20.2 Master Name Server
birch.coniferous.trees.ops 172.30.20.3 Slave Name Server
popular.coniferous.trees.ops 172.30.20.5 SMTP mail Server
maple.coniferous.trees.ops 172.30.20.6 IMAP mail Server
oak.coniferous.trees.ops 172.30.20.8 Samba Server


Firewall Policies

Perform the following steps for this section:

  1. Make certain that you have iptables services enabled and running instead of Firewalld.
  2. Modify the iptables to meet the following conditions:
  • All outgoing traffic is allowed.
  • Responses to any traffic the machine sends out are allowed.
  • Traffic on the loopback interface is allowed.
  • The host machine (and only the host machine) must be able to ssh to that cloning-source VM.
  • ICMP traffic is allowed if it originated with the local network only.
  • As this is acting as the secure basis for later machines, no other traffic should be allowed.

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