572
edits
Changes
m
#forwarders { 208.67.222.222; }; # This one works at home #forwarders { 10.102.100.21; }; # This one works at Seneca
'''Depending on your professor you will either be asked to submit the lab in class, or online. Follow the appropriate set of instructions below.''' ===Online Submission (Ahad Mammadov's Classes only)===
→Installation
== Installation ==
Install Bind '''bind''' on your '''host''' machine.
== Configuration ==
directory "/var/named/";
allow-query {127.0.0.1; 192.168.XX.0/24;};
};
zone "localhost" {
=== Zone file ===
Now edit '''/var/named/mydb-for-yoursenecaid-ops''' and enter the following (use your own X XX value and domain where applicable).
<pre>
{{Admon/important |Host Command Doesn't Work|Your machines do not know what domain to automatically add to the end of hostnames (or believe they are still in the seneca domain). The '''SEARCH''' (or DOMAIN) parameter in the '''ifcfg-eth0''' file is used to specify your own domain (eg. '''yoursenecaid.ops''' ).<br><br>}}
<li> Add the '''SEARCH''' (or DOMAIN) parameter for your '''ifcfg-eth0''' file as shown above for your '''host''' machine.</li>
<li> Issue the '''host ''' command for all vm names and host name to make certain that is works.</li>
<li>Also on all of the VMs, install and use a text-based browser called '''lynx''' to access the Web, and test-out to see if it works by issuing the command '''lynx''' with the URL as an argument.</li><li>Experiment with the following commands:<br>
<source>
As it stands now, your server will only handle forward resolution (converting names into addresses), but it is also sometimes necessary to convert addresses back into human readable names. For public IP addresses only your ISP can provide this service for you. For private networks you can set it up for your own organisation. But even if you're setting up reverse DNS on the public internet - you need to understand what information the ISP would require.
Issue the following commands on any of your VMs (once again replacing X XX with your network octet):
<source>
host 192.168.XXX.1host 192.168.XXX.2host 192.168.XXX.3host 192.168.XXX.4</source>
Each one should have failed because there is currently nothing that will handle this reverse lookup for you. This requires another zone on your server.
Add the following entry to your '''/etc/named.conf''' (once again replacing X XX with your own octet):
<pre>
zone "XXX.168.192.in-addr.arpa." {
type master;
file "mydb-for-192.168.XXX";
};
</pre>
1D ; Negative Cache TTL
);
@ IN NS host.yoursenecaid.ops.1 IN PTR host.yoursenecaid.ops.
</pre>
</ol>
{{Admon/important |Backup your VMs!|You MUST perform a '''full backup''' of ALL of your VMs whenever you complete your '''OPS335 labs''' or when working on your '''OPS335 assignments'''. You should be using the dump or rsync command, and you should use the Bash shell script that you were adviced to create in order to backup all of your VMs.}}
= COMPLETING THE LAB =
You have now gained experience with some common configuration settings for named, as well as common resource records.
Follow the instructions for lab 3 on blackboard.
<!--
===Andrew's sections===
::<span style="color:green;font-size:1.5em;">✓</span>Download and run '''https://ict.senecacollege.ca/~andrew.smith/ops335/labcheck3.bash'''
::<span style="color:green;font-size:1.5em;">✓</span>Completed Lab3 log-book notes.
-->
=EXPLORATION QUESTIONS=
