932
edits
Changes
m
# You should '''NOT''' set your Host Machine to use '''vm1''' as the DNS server. DNS is a critical component of your network setup and if it's not working right - you won't even be able to look for a solution online (or get to this wiki page) on your host. Also your host is configured to be a DHCP client and it gets its DNS server assigned automatically.
{{Admon/important |Run vm1 (for DNS server) for Future labs|Due to the changes made in this lab, you will now need your vm1 running in order for any of your virtual machines to be able to use the internet.}}
Moving DNS server onto host - investigation 2
= INVESTIGATION 2: CONFIGURING THE DNS CLIENT =
Before proceeding, we need to set the primary DNS server (DNS1 ) in your '''ifcfg-eth0''' (or ''ifcfg-en0'') file for your network interface cards for your virtual machines. Also it is a good idea to install the '''bind-utils''' package on those other VMs as well in order to perform queries on your vm1 host domain name server.
'''Perform the following Steps:'''
#Only install Install the '''bind-utils''' package for your '''vm2''' and '''vm3''' virtual machines.#You will need to configure your '''vm2''' and '''vm3''' VMs to use vm1your host's IPADDR as the '''default DNS server''' (DNS1) in your '''ifcfg-eth0''' (or ''ifcfg-en0'') file for your network interface card.<br>You should know how to do that, but if you forgot the procedure, refer to [http://zenit.senecac.on.ca/wiki/index.php/OPS335_Lab_1#Making_Persistent_.28Permanent.29_Network_Setting_Changes Lab 1].
#Modify the hostname of '''each machine''' (host and all three VMs) to match what the DNS server says it is (including the domain). This will be important for services we configure in later labs.
== Testing ==
nslookup
dig</source>Use the '''dig''' command to query your DNS server for specific records (up to this point you only have NS, A, and SOA records).</li></ol>
'''Record steps, commands, and your observations in INVESTIGATION 2 in your OPS335 lab log-book'''
