Changes

Jump to: navigation, search

OPS335 Lab 3

51 bytes added, 10:02, 9 February 2016
no edit summary
= INVESTIGATION 2: CONFIGURING THE DNS CLIENT =
Before proceeding, we should need to install and configure '''bind ''' on the other virtual machines ('''vm2''' and '''vm3'''), as well as specifying the primary domain server ('''DNS1''') in your '''ifcfg-eth0''' (or ''ifcfg-en0'') network interface cards for your virtual machines. This will allow us to perform DNS queries on all of our VMs.
'''Perform the following Steps:'''
#Repeat the procedures to install '''bind''' , <u>edit</u> the appropriate configuration and data files for your '''vm2''' and '''vm3''' machines.
#Make certain that you correctly start and enable the named service on those virtual machines.
#Now that youYou will need to configure your '''ve setup a DNS server on vm2'''vm1and '''vm3''', you will need to configure all your VMs to use that as the '''default DNS server'''. 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].
You can , but you shouldn't , set your host 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.
== Testing ==
13,420
edits

Navigation menu