1,234
edits
Changes
→Purpose
In this lab you will configure a Linux machine to be a DNS server for the rest of the machines in your intranet. You'll '''use <u>your</u> MySeneca ID as your domain'''. The server will handle all queries for names in the '''yoursenecaid.org''' domain. The server will pass DNS queries for other names and addresses out to the Internet (i.e. to Seneca's DNS server).
This is the current state of our internal network when your harddrive is plugged into a lab machine. Note that if any of the listed services aren't working for you - you should fix them (especially your iptables - which may block DNS traffic needed for this lab):
[[Image:Lab2network.png]]
You can see in the diagram above that when one of your VMs does a name resolution request:
* The VM contacts the host, which is running a DNS proxy, not a full DNS server
* The DNS proxy on the host contacts the Seneca DNS server, which was assigned to be used on the host via DHCP
* Depending on the request - the Seneca DNS server may contact other DNS servers to get the answer to the request.
After you're finished with this lab - your vm1 will be running a full-featured DNS server, which is how you're going to get the '''yoursenecaid.org''' domain without paying for it. Unfortunately you'll be the only one using your DNS server so noone else will be able to resolve hosts under '''yoursenecaid.org'''
===DNS Resources===
