Difference between revisions of "OPS335 Assignment 1b - Murray Saul"
(→Set-up Master Name Server (elm)) |
(→Set-up Master Name Server (elm)) |
||
Line 18: | Line 18: | ||
Perform the following steps for this section: | Perform the following steps for this section: | ||
− | #Clone the '''elm''' virtual machine from the seedling cloning-source. Refer to the table below for '''address''' and '''hostname'''. | + | #Clone the '''elm''' virtual machine 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'''. | #Create a '''regular user''' for this virtual machine using '''your Seneca userID'''. | ||
#Setup a DNS server on your elm virtual machine with noting the following items below:<ol type="a"><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>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.</li><li>Only this Master Name Server (elm) will be allowed to transfer zone files from this machine.</li><li>As you will now have a functioning primary DNS server, modify your network configuration file to specify its new IPADDR.</li></ol> | #Setup a DNS server on your elm virtual machine with noting the following items below:<ol type="a"><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>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.</li><li>Only this Master Name Server (elm) will be allowed to transfer zone files from this machine.</li><li>As you will now have a functioning primary DNS server, modify your network configuration file to specify its new IPADDR.</li></ol> |
Revision as of 07:58, 29 January 2017
Contents
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:
- Clone the elm virtual machine 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 elm virtual machine with noting the following items below:
- 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.
- 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.
- Only this Master Name Server (elm) will be allowed to transfer zone files from this machine.
- As you will now have a functioning primary DNS server, modify your network configuration file to specify its new IPADDR.
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.
Clone "ns2" VM from "Cloning Source" & Perform Setup Tasks
Perform the following steps for this section:
- 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.
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):
- 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. - 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.