* vm3.yoursenecaid.org
Note that these are settings that are local to each mahcine, e.g. you will still not be able to contact vm1.yoursenecaid.org from vm3.yoursenecaid.org. That's because currently you're using the Seneca and other public DNS servers which know nothing about yoursenecaid.org
===Perform these steps on This preparation step is in fact unnecessary to complete our goal for the lab (do you know why?) but it will make things look more consistent, which will make your gateway/firewall===life a little easier.
#Start up your host machine, open a terminal window and "su -" to root. This PC will be named "host". It will be your gateway/firewall.#Ensure you are connected to the Internet. Use Firefox to authenticate yourself so you can surf the web outside of the Seneca domain.#Use yum to update your system if necessary:<br><pre>yum update</pre>#If you have not already done so, permanently set the host name of the 'host' machine to "'''host.seneca-id.org'''" (Use '''<u>your</u> seneca-id''' there instead of the literal word ''seneca-id'')!== Installation ==
===Perform these steps on your VM1===#Start your VM 1. This machine will be Use yum to install the domain name DNS server for your intranet.#On the VMWe'll be using Bind, Use yum to update your system if necessary:<br><pre>yum update</pre>#Use yum to install the most popular DNS server:<br><pre>yum install bind</pre>on the planet.
===Edit /etc/named.conf===
'''Record troubleshooting checklist for INVESTIGATION 1 in your OPS335 lab log-book'''
==INVESTIGATION 2: CONFIGURING DNS (CLIENT SIDE - Centos7 Host Machine)==
