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 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.xconiferous.trees.ops'''.</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.