Changes

Jump to: navigation, search

OPS335 DNS Lab

9 bytes added, 14:02, 30 January 2016
no edit summary
host 192.168.X.4
<ol><li value="4">Now configure your other virtual machines to also use VM 1 as their DNS server.</li><li>Also 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 work:<br><br></li></ol>
host
{{Admon/important| This final step is important. | Failure to complete this will cause problems 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 use. Double check that this address, and the ability to search using your DNS server, persist after reboot.</li><li>On each machine add the entry to your interface configuration file that will cause it to permanently use your VM 1 as its primary DNS server.</li><li>If you 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 and by name (hostname only, and hostname with domain).</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>
13,420
edits

Navigation menu