13,420
edits
Changes
no edit summary
== Purpose ==
In this assignment, you will use the '''335assign''' virtual network and the '''cloyne''' cloning-source that you created in assignment 1 (part 1) to create two name-servers. One of the cloned VMs (hostname: '''piketoronto''') 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 ==
{{Admon/important|It is YOUR responsibility to Backup all of your VMs for this Assignment!|You are required to frequently backup your VMs prior to exiting a work session during this assignment. Your instructor will NOT accept the fact that your hard disk crashed and lost all of your work. If you properly backed up your VM images and xml configuration files to a USB, then you can purchase a new hard-disk or wipe and recreate your hard disk and restore your VMs. }}<br />
=== Set-up Master Name Server ('''piketoronto''')===
Perform the following steps for this section:
#Create a clone virtual machine called '''piketoronto''' from the '''cloyne''' 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 '''piketoronto''' 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 '''bass.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 ('''pickerel''') ===
#Create a clone virtual machine called '''pickerel''' from the '''cloyne''' 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:<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 '''piketoronto.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 ===
| style="background-color:#66cccc; border: 2px solid black;" |'''Cloning-source''' used to create other servers for other assignments.
|-style="background-color:#66cccc; border: 2px solid black;"
| style="background-color:#66cccc; border: 2px solid black;" | '''piketoronto.species.lake.ops'''
| style="background-color:#66cccc; border: 2px solid black;" | ''' 172.17.15.2'''
| style="background-color:#66cccc; border: 2px solid black;" | '''Master''' Name Server
In addition to the basic firewall established in assignment 1, ensure the following restrictions are met:
# Any machine may query '''piketoronto'''
# Only the machines in the '''species.lake.ops''' network may query pickerel.
|-
|
::'''piketoronto''' and '''pickerel''' VMs created
| style="text-align:right" | /1
|-
|
::'''piketoronto''' and '''pickerel''' VMs can perform '''DNS queries of vm1, vm2, vm3'''
| style="text-align:right" | /1
|-
|
::'''piketoronto''' and '''pickerel''' VMs can perform '''forward DNS lookups''' for ALL machines within network (listed in the table above)
| style="text-align:right" | /3
|-
|
::'''piketoronto''' and '''pickerel''' VMs can perform '''reverse DNS lookups''' for ALL machines within network (listed in the table above)
| style="text-align:right" | /3
|-
| width=10% style="text-align:right;font-weight:bold" | Mark
|-
| colspan=2 style="background-color:#eeeeee;"| '''Master Name Server (piketoronto) - Network Configuration'''
|-
|
| style="text-align:right" | /5
|-
| colspan=2 style="background-color:#eeeeee;"| '''Master Name Server (piketoronto) - Named Configuration Options / Zone Declarations'''
|-
|
|-
|
::pike toronto server is the '''master''' name-server for species.lake.ops
| style="text-align:right" | /1
|-
| colspan=2 style="background-color:#eeeeee;"| '''Master Name Server (piketoronto) - Zone Record'''
|-
|
|-
|
::'''piketoronto''' allows queries from any machine (i.e. will work with '''vm1''', '''vm2''', '''vm3''')
| style="text-align:right" | /2
|-
