Changes

Jump to: navigation, search

OPS335 DNS Lab

1,318 bytes removed, 03:44, 3 February 2016
INVESTIGATION 2: CONFIGURING THE DNS CLIENT
= INVESTIGATION 2: CONFIGURING THE DNS CLIENT =
Now that we have you've setup a DNS server on your virtual machine (vm1), we will - you need to configure all our VMs to use that as the default DNS server. You should know how to do that, if you forgot - go back to [[OPS335_Lab_1 | Lab 1]] to remind yourself.
You should know how can but you shouldn't set your host to do that, use vm1 as the DNS server. DNS is a critical component of your network setup and if it's not working right - you forgot - go back won't even be able to look for a solution online (or get to [[OPS335_Lab_1 | Lab 1]] this wiki page) on your host. Also your host is configured to remind yourselfbe a DHCP client and it gets its DNS server assigned automatically.
'''Perform the following steps on your Centos host:'''== Testing ==
<ol><li value="1">Edit the '''/etc/resolv.conf''' file and enter the The following:<pre>nameserver 192.168.X.2domain '''seneca-id'''.org</pre></li><li>Now try the commands:<pre>host host.'''seneca-id'''.orghost vm1.'''seneca-id'''.orghost vm2.'''seneca-id'''.orghost vm3.'''seneca-id'''.orghost yahoo.ca</pre><pre>host 192.168.X.1host 192.168.X.2host 192.168.X.3host 192.168.X.4</pre></li></ol><ol><li value="4">Now configure your other virtual machines to also use VM 1 should work as their DNS server.</li><li>Also expected on the VMs use a text browser such as lynx to access the Web.<br><br>(NOTE: you do not need to authenticate yourself through SeneNet on this machine, as they connects through the host which is already authenticated)</li><li>On all machines in your network, experiment with the following commands. Be sure to use several different command options to learn and understand how they workVMs:<br><br><pre>hostdignslookup</pre></li></ol>
<source lang="bash">
host host.yoursenecaid.org
host yoursenecaid.org
host yoursenecaid.org
host yoursenecaid.org
host google.ca
</source>
Also on the VMs use a text browser such as lynx to access the Web.
{{Admon/important| These final steps are important!| Failure to complete this will cause problems Experiment with future labs.}}  <ol><li value="7">Finally, ensure each machine is using the static IP address and hostname that matches what the DNS server now claims they usefollowing commands. Double check that this address, and Use the ability '''dig''' command to search using query your DNS server, persist after reboot.</li><li>On each machine add the entry for specific records (up to your interface configuration file that will cause it to permanently use your VM 1 as its primary DNS server.</li><li>If this point you only have made any changes to the /etc/hosts file, undo them. Your machines must be relying on your DNS server.</li><li>Ensure that your machines can ping and SSH to each other by IP address NS and by name (hostname only, and hostname with domainA records).</li><li>Modify the ifcfg file on your host so that it will still get a DHCP address, but ignore the DNS information given to it by the DHCP server in favour of the domain and DNS information you provide it.</li></ol>  '''Record troubleshooting checklist for INVESTIGATION 2 in your OPS335 lab log-book'''
== COMPLETING THE LAB ==

Navigation menu