13,420
edits
Changes
→Set-up slave Name Server (birch)
#Create a clone virtual machine called '''birch''' 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:<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 30 minutes.</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>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>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.
#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.
=== Reference Materials: List of Machines / DNS Records ===