Franske ITC-2480 DNS Lab - Revision history

BenFranske: Update to mjnk version

2021-12-03T19:59:47Z

Update to mjnk version

BenFranske: /* Install BIND & Enable Caching */ update dns address

2020-03-25T14:04:07Z

Install BIND & Enable Caching: update dns address

← Older revision		Revision as of 14:04, 25 March 2020
Line 13:		Line 13:
	// 0.0.0.0;		// 0.0.0.0;
	// };</pre>		// };</pre>
	* Note that you will also need to replace 0.0.0.0 with 172.17.139.10 for outside DNS lookups to function correctly.</li>		* Note that you will also need to replace 0.0.0.0 with 172.17.139.11 for outside DNS lookups to function correctly.</li>
	<li>The reason we setup a forwarder address is so that domain requests that are not on our system are passed to another DNS server instead of being searched against the root nameservers. You may want to do this in domain or enterprise environments as most large networks have internal domain names setup that only redirect inside of a local LAN. By using a forwarder, as long as the DNS server you push requests to is able to access those internal records, you will be able to access local content from internal domain names instead of needing to rely on IP addresses.</li>		<li>The reason we setup a forwarder address is so that domain requests that are not on our system are passed to another DNS server instead of being searched against the root nameservers. You may want to do this in domain or enterprise environments as most large networks have internal domain names setup that only redirect inside of a local LAN. By using a forwarder, as long as the DNS server you push requests to is able to access those internal records, you will be able to access local content from internal domain names instead of needing to rely on IP addresses.</li>
	<li>To apply this change, you will need to restart the BIND server. to do this run '''service bind9 restart''' with administrative permissions.</li>		<li>To apply this change, you will need to restart the BIND server. to do this run '''service bind9 restart''' with administrative permissions.</li>

BenFranske: /* Manually editing a zone file */

2018-02-24T02:16:37Z

Manually editing a zone file

← Older revision		Revision as of 02:16, 24 February 2018
Line 118:		Line 118:
	<li>Now, with your favorite text editor, open up the file which corresponds to the ''debserv-*.test'' domain. It should look similar to this:		<li>Now, with your favorite text editor, open up the file which corresponds to the ''debserv-*.test'' domain. It should look similar to this:
	<pre>$ttl 38400		<pre>$ttl 38400
	debserv-A.test. IN SOA ~~VMHostname~~. root.debserv-A.test. (		debserv-Z.test. IN SOA 2480-Z.itc2480.campus.ihitc.net. root.debserv-Z.test. (
	~~1395013947~~		1519434495
	10800		10800
	3600		3600
	604800		604800
	38400 )		38400 )
	debserv-A.test. IN NS ~~VMHostname~~.		debserv-Z.test. IN NS 2480-Z.itc2480.campus.ihitc.net.
	debserv-A.test. IN A 172.17.50.~~XXX~~		debserv-Z.test. IN A 172.17.50.36
	debserv-A.test. IN MX 10 172.17.50.~~XXX~~		debserv-Z.test. IN MX 10 mail.debserv-Z.test.
	~~cname~~.debserv-A.test. IN CNAME debserv-A.test.</pre></li>		mail.debserv-Z.test. IN A 172.17.50.36
	<li>Notice the formatting for domain records. Each record is defined by the domain or subdomain name, ''IN'', then the record type (like A, NS, or MX), followed by what the record is pointed to.</li>		blog.debserv-Z.test. IN CNAME debserv-z.test.
			debserv-Z.test. IN AAAA 2607:f930:1c00:50:250:56ff:feb1:8756
			mail.debserv-Z.test. IN AAAA 2607:f930:1c00:50:250:56ff:feb1:8756</pre></li>
			<li>Notice the formatting for domain records. Each record is defined by the domain or subdomain name, ''IN'', then the record type (like A, AAAA, NS, or MX), followed by what the record is pointed to.</li>
	<li>For this example, we want to change the MX priority from 10 to 15, so change the MX record settings using your text editor.</li>		<li>For this example, we want to change the MX priority from 10 to 15, so change the MX record settings using your text editor.</li>
	<li>When you are done, restart the bind9 service to reload the changes.		<li>When you are done, restart the bind9 service to reload the changes.
	* Note: when restarting bind, if you have any errors restarting the service this normally means you have a typo in one of your zone files. If this is the case, go through the file again in a text editor to make sure you did not add anything extra or remove anything else.</li>		* Note: when restarting bind, if you have any errors restarting the service this normally means you have a typo in one of your zone files. If this is the case, go through the file again in a text editor to make sure you did not add anything extra or remove anything else.</li>
	<li>Use the '''dig''' tool to check the MX record and see that the new priority is active. You should see something similar to the following response:		<li>Use the '''dig''' tool to check the MX record and see that the new priority is active. You should see something similar to the following response:
	<pre>; <<>> DiG 9.8.4-~~rpz2+rl005.12~~-P1 <<>> MX debserv-*.test ~~@127.0.0.1~~		<pre>; <<>> DiG 9.10.3-P4-Debian <<>> debserv-z.test MX
	;; global options: +cmd		;; global options: +cmd
	;; Got answer:		;; Got answer:
	;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: ~~59875~~		;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40128
	;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0		;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 3

			;; OPT PSEUDOSECTION:
			; EDNS: version: 0, flags:; udp: 4096
	;; QUESTION SECTION:		;; QUESTION SECTION:
	;debserv-*.test. IN MX		;debserv-z.test. IN MX

	;; ANSWER SECTION:		;; ANSWER SECTION:
	debserv-.test. 38400 IN MX 15 ~~172.17.50.XXX~~.debserv-.test.		debserv-Z.test. 38400 IN MX 15 mail.debserv-Z.test.

	;; AUTHORITY SECTION:		;; AUTHORITY SECTION:
	debserv-*.test. 38400 IN NS ~~VMHostname~~.		debserv-Z.test. 38400 IN NS 2480-Z.itc2480.campus.ihitc.net.

	;; Query time: 4 msec		;; ADDITIONAL SECTION:
			mail.debserv-Z.test. 38400 IN A 172.17.50.36
			mail.debserv-Z.test. 38400 IN AAAA 2607:f930:1c00:50:250:56ff:feb1:8756

			;; Query time: 0 msec
	;; SERVER: 127.0.0.1#53(127.0.0.1)		;; SERVER: 127.0.0.1#53(127.0.0.1)
	;; WHEN: ~~Sun Mar 16~~ 20:40:~~02 2014~~		;; WHEN: Fri Feb 23 20:15:48 CST 2018
	;; MSG SIZE rcvd: 78</pre></li>		;; MSG SIZE rcvd: 163</pre></li>
	<li>Notice how the Answer Section shows the MX record is pointed to the IP of the domain, and that the priority is set to 15.</li>		<li>Notice how the Answer Section shows the MX record is pointed to the IP of the domain, and that the priority is set to 15.</li>
	<li>Congratulations, you have now setup a functional DNS server.</li>		<li>Congratulations, you have now setup a functional DNS server.</li>

BenFranske: /* Create a Domain using Webmin */

2018-02-24T01:57:02Z

Create a Domain using Webmin

← Older revision		Revision as of 01:57, 24 February 2018
Line 44:		Line 44:
	Email address: root@debserv-*.test</pre></li>		Email address: root@debserv-*.test</pre></li>
	<li>Click the ''create'' button to add the domain. As this point you should now be on the ''Edit Master Zone'' page. From here you can add and edit domain records for this domain name.</li>		<li>Click the ''create'' button to add the domain. As this point you should now be on the ''Edit Master Zone'' page. From here you can add and edit domain records for this domain name.</li>
	<li>To create our ''A record'' which points your domain to an IP address, click the ''Address'' button. For the ''Name'' enter ''@''. The ''@'' symbol in DNS Zones defines the parent domain (alternatively you could re-enter the parent domain ''debserv-*.test.'' with the period at the end). In the ''address'' field enter your VM's static IP set in [[Franske ITC-2480 Lab 5\|Lab 5]] and click ''Create''. Return to the main BIND DNS Server page. Click the ''Apply Configuration'' link in the top right corner.</li>		<li>To create our ''A record'' which points your domain to an IP address, click the ''Address'' button. For the ''Name'' enter ''@''. The ''@'' symbol in DNS Zones defines the parent domain (alternatively you could re-enter the parent domain ''debserv-*.test.'' with the period at the end). In the ''address'' field enter your VM's static IP set in [[Franske ITC-2480 Lab 5\|Lab 5]] and click ''Create''. Return to the main BIND DNS Server page. Click the ''Apply Configuration'' link (which looks like two arrows chasing each other) in the top right corner. You'll see the "Apply Configuration" text if you hover your mouse over the button.</li>
	<li> To test the record use '''nslookup''' or '''dig''' to lookup the domain you just created, which should be ''debserv-.test'' by entering '''nslookup debserv-.test''' or '''dig debserv-.test''' (don't forget to replace the with your System ID letter).		<li> To test the record use '''nslookup''' or '''dig''' to lookup the domain you just created, which should be ''debserv-.test'' by entering '''nslookup debserv-.test''' or '''dig debserv-.test''' (don't forget to replace the with your System ID letter).
	* If you have issues looking up the domain, make sure that the system is still using 127.0.0.1 as the DNS server. If not, check your ''/etc/resolv.conf'' file.</li>		* If you have issues looking up the domain, make sure that the system is still using 127.0.0.1 as the DNS server. If not, check your ''/etc/resolv.conf'' file.</li>
	</ol>		</ol>

	== Additional DNS Record Types ==		== Additional DNS Record Types ==
	<ol>		<ol>

BenFranske: /* Additional DNS Record Types */

2018-02-24T01:48:22Z

Additional DNS Record Types

← Older revision		Revision as of 01:48, 24 February 2018
Line 78:		Line 78:
	When done, press ''Create Now''.		When done, press ''Create Now''.
	<li> When you are back at the ''Apache Webserver'' page, then click ''Apply Changes'' in the top right.</li>		<li> When you are back at the ''Apache Webserver'' page, then click ''Apply Changes'' in the top right.</li>
	<li>Now in a SSH session, open up your favorite command line web browser like '''links''' and visit ''blog.debserv-*.test''. Notice how you are now visiting the blog directly, instead of your modified index.html file. This is because we setup a virtual host in Apache that listens for requests to the CNAME we created and points to the document root where the Wordpress software is installed.		<li>Now in a SSH session, open up your favorite command line web browser like '''links''' and visit ''blog.debserv-*.test.'' make special note that when you enter the URL in Links you need to include the extra period at the end. This is because the .test domain is not a regular TLD like .com .org etc. and the Links browser doesn't know how to handle it unless we force it as a domain name by adding the period at the end. This is not related to it being a CNAME or our Apache configuration and with a regular domain name would not be required. Notice how you are now visiting the blog directly, instead of your modified index.html file. This is because we setup a virtual host in Apache that listens for requests to the CNAME we created and points to the document root where the Wordpress software is installed.
	* Note that you will not be able to use this URL to access the blog from your local PC yet because your local PC isn't using your Linux server as it's DNS server and the .test domain isn't registered to your DNS server.</li>		* Note that you will not be able to use this URL to access the blog from your local PC yet because your local PC isn't using your Linux server as it's DNS server and the .test domain isn't registered to your DNS server.</li>
	<li>Congrats, at this point you have a basic domain working with a MX, CNAME, and A record.</li>		<li>Congrats, at this point you have a basic domain working with a MX, CNAME, and A record.</li>

BenFranske: /* Install BIND & Enable Caching */

2018-02-23T23:09:12Z

Install BIND & Enable Caching

← Older revision		Revision as of 23:09, 23 February 2018
Line 28:		Line 28:
	* Notice how it shows it is using 127.0.0.1 as the server. If you do not see this, then your interface file or resolv.conf file is not set to use the local machine for DNS lookups. Note also that the IP address returned for this domain may vary from the one shown in the output above.</li>		* Notice how it shows it is using 127.0.0.1 as the server. If you do not see this, then your interface file or resolv.conf file is not set to use the local machine for DNS lookups. Note also that the IP address returned for this domain may vary from the one shown in the output above.</li>
	<li>Experiment using the '''dig''' utility to check DNS name resolution which can provide more detailed output than '''nslookup'''. Run '''dig inverhills.edu''' and see if you can find where the IP address for the domain is reported in the output as well as where the server IP address is reported in the output.</li>		<li>Experiment using the '''dig''' utility to check DNS name resolution which can provide more detailed output than '''nslookup'''. Run '''dig inverhills.edu''' and see if you can find where the IP address for the domain is reported in the output as well as where the server IP address is reported in the output.</li>
			<li>Now would be a good time to reboot your server to ensure the DNS server network interface configuration changes remain permanent. Use the appropriate '''shutdown''' command to reboot the system. If you've forgotten how to reboot you could check the ''man'' page for the '''shutdown''' command.</li>
			<li>Once the system reboots log back in and use '''nslookup''' or '''dig''' to verify the default nameserver being used is ''127.0.0.1''.</li>
	</ol>		</ol>

	== Create a Domain using Webmin ==		== Create a Domain using Webmin ==
	<ol>		<ol>

BenFranske: /* Manually editing a zone file */

2018-02-23T23:05:59Z

Manually editing a zone file

← Older revision		Revision as of 23:05, 23 February 2018
Line 109:		Line 109:

	== Manually editing a zone file ==		== Manually editing a zone file ==
	# Lastly we are going to look at the domain zone file. While ~~webmin~~ provides a nice interface to add records, all it is doing is manually adding our records to our zone file. When you use BIND for DNS, every domain created gets its own record file which is called the zone file. In this file all subdomains and records are stored for said domain.		<ol>
	# By default, the location for these records will be in /var/lib/bind, so ~~cd into~~ that ~~folder~~ and ls the contents.		<li>Lastly we are going to look at the domain zone file. While Webmin provides a nice interface to add records, all it is doing is manually adding our records to our text based zone file. When you use BIND for DNS, every domain created gets its own record file which is called the zone file. In this file all subdomains and records are stored for said domain.</li>
	# Now, with your favorite text editor, open up the file. It should look similar to this:		<li>By default, the location for these records on Debian will be in ''/var/lib/bind'', so go to that directory and list the contents.</li>
			<li>Now, with your favorite text editor, open up the file which corresponds to the ''debserv-*.test'' domain. It should look similar to this:
	<pre>$ttl 38400		<pre>$ttl 38400
	debserv-A.test. IN SOA VMHostname. root.debserv-A.test. (		debserv-A.test. IN SOA VMHostname. root.debserv-A.test. (
Line 121:		Line 122:
	debserv-A.test. IN NS VMHostname.		debserv-A.test. IN NS VMHostname.
	debserv-A.test. IN A 172.17.50.XXX		debserv-A.test. IN A 172.17.50.XXX
	debserv-A.test. IN MX 1 172.17.50.XXX		debserv-A.test. IN MX 10 172.17.50.XXX
	cname.debserv-A.test. IN CNAME debserv-A.test.</pre>		cname.debserv-A.test. IN CNAME debserv-A.test.</pre></li>
	# Notice the formatting for domain records. Each record is defined by the domain or subdomain, IN, then the record type, followed by what the record is pointed to.		<li>Notice the formatting for domain records. Each record is defined by the domain or subdomain name, ''IN'', then the record type (like A, NS, or MX), followed by what the record is pointed to.</li>
	# For this example, we want to change the MX priority from 1 to 10, so change the MX record settings using your text editor.		<li>For this example, we want to change the MX priority from 10 to 15, so change the MX record settings using your text editor.</li>
	# When you are done, restart the bind9 service to reload the changes~~. We will now use a new command, dig, to lookup the record to make sure the changes were applied correctly~~.		<li>When you are done, restart the bind9 service to reload the changes.
	* Note: when restarting bind, if you have any errors restarting the service this normally means you have a typo in one of your zone files. If this is the case, go through the file again in a text editor to make sure you did not add anything extra.		* Note: when restarting bind, if you have any errors restarting the service this normally means you have a typo in one of your zone files. If this is the case, go through the file again in a text editor to make sure you did not add anything extra or remove anything else.</li>
	# dig ~~is a very powerful DNS~~ tool ~~that allows you~~ to ~~lookup specific records for DNS domains, as well as many other things such as PTR, or reverse records. For our reasons though, we will use it to lookup~~ the ~~edited~~ MX record~~. To do this, run "dig MX debserv-*.test".~~		<li>Use the '''dig''' tool to check the MX record and see that the new priority is active. You should see something similar to the following response:
	* Note: If you are having issues, add @127.0.0.1 to the ~~end of the dig command to force dig to use the local DNS server~~.
	# You should see the following response:
	<pre>; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> MX debserv-*.test @127.0.0.1		<pre>; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> MX debserv-*.test @127.0.0.1
	;; global options: +cmd		;; global options: +cmd
Line 140:		Line 139:

	;; ANSWER SECTION:		;; ANSWER SECTION:
	debserv-.test. 38400 IN MX 10 172.17.50.XXX.debserv-.test.		debserv-.test. 38400 IN MX 15 172.17.50.XXX.debserv-.test.

	;; AUTHORITY SECTION:		;; AUTHORITY SECTION:
Line 148:		Line 147:
	;; SERVER: 127.0.0.1#53(127.0.0.1)		;; SERVER: 127.0.0.1#53(127.0.0.1)
	;; WHEN: Sun Mar 16 20:40:02 2014		;; WHEN: Sun Mar 16 20:40:02 2014
	;; MSG SIZE rcvd: 78</pre>		;; MSG SIZE rcvd: 78</pre></li>
	# Notice how the Answer Section shows the MX record is pointed to the IP of the domain, and that the priority is set to 10.		<li>Notice how the Answer Section shows the MX record is pointed to the IP of the domain, and that the priority is set to 15.</li>
	~~# Congrats~~, you have now setup a functional DNS server.		<li>Congratulations, you have now setup a functional DNS server.</li>

BenFranske: /* Additional DNS Record Types */

2018-02-23T22:59:08Z

Additional DNS Record Types

← Older revision		Revision as of 22:59, 23 February 2018
Line 51:		Line 51:
	</li>To create a MX record we will use Webmin again. In Webmin on the ''BIND DNS Server'' page, click the domain on the bottom named ''debserv-.test'' and then click the ''Mail Server'' button. Under ''name'', enter ''@'' again, and for ''mail server'' enter ''mail.debserv-.test.'' (with the period at the end). For ''Priority'', enter ''10''.		</li>To create a MX record we will use Webmin again. In Webmin on the ''BIND DNS Server'' page, click the domain on the bottom named ''debserv-.test'' and then click the ''Mail Server'' button. Under ''name'', enter ''@'' again, and for ''mail server'' enter ''mail.debserv-.test.'' (with the period at the end). For ''Priority'', enter ''10''.
	* This entry has said we want other servers trying to send mail to ''users@debserv-.test'' to actually send it to the server at ''mail.debserv-.test'' which allows us to use a different server for email than we use fore web serving, etc.		* This entry has said we want other servers trying to send mail to ''users@debserv-.test'' to actually send it to the server at ''mail.debserv-.test'' which allows us to use a different server for email than we use fore web serving, etc.
	* The Priority entry allows people to define more than 1 MX record for a name, and the order which the sending service will try to use for contacting the various mail servers at your domain.</li>		* The Priority entry allows people to define more than one MX record for a name, and the order which the sending service will try to use for contacting the various mail servers at your domain.</li>
	<li>Go back to the domain zone overview page. Because we don't currently have an "A" (address) record for ''mail.debserv-.test'' the mail would currently go undelivered. Add an ''A'' record for ''mail.debserv-.test'' which points to the IP of your system.</li>		<li>Go back to the domain zone overview page. Because we don't currently have an "A" (address) record for ''mail.debserv-.test'' the mail would currently go undelivered. Add an ''A'' record for ''mail.debserv-.test'' which points to the IP of your system.</li>
	<li> To test an ''MX'' record we need to make multiple queries and ask '''nslookup''' or '''dig''' to fist check for MX records for the domain like '''nslookup -type=MX debserv-.test''' or '''dig debserv-.test MX''' which will return the names of the mail servers for that domain. We then need to do a regular '''nslookup''' or '''dig''' on those names to determine what IP addresses those are pointed to. Of course, for mail to actually work we'd also need to insure mail server software is installed and configured on that server as well.</li>		<li> To test an ''MX'' record we need to make multiple queries and ask '''nslookup''' or '''dig''' to fist check for MX records for the domain like '''nslookup -type=MX debserv-.test''' or '''dig debserv-.test MX''' which will return the names of the mail servers for that domain. We then need to do a regular '''nslookup''' or '''dig''' on those names to determine what IP addresses those are pointed to. Of course, for mail to actually work we'd also need to insure mail server software is installed and configured on that server as well.</li>
Line 79:		Line 79:
	<li>Congrats, at this point you have a basic domain working with a MX, CNAME, and A record.</li>		<li>Congrats, at this point you have a basic domain working with a MX, CNAME, and A record.</li>
	</ol>		</ol>

	== Adding a AAAA record ==		== Adding a AAAA record ==
	<ol>		<ol>

BenFranske at 22:57, 23 February 2018

2018-02-23T22:57:31Z

← Older revision		Revision as of 22:57, 23 February 2018
Line 53:		Line 53:
	* The Priority entry allows people to define more than 1 MX record for a name, and the order which the sending service will try to use for contacting the various mail servers at your domain.</li>		* The Priority entry allows people to define more than 1 MX record for a name, and the order which the sending service will try to use for contacting the various mail servers at your domain.</li>
	<li>Go back to the domain zone overview page. Because we don't currently have an "A" (address) record for ''mail.debserv-.test'' the mail would currently go undelivered. Add an ''A'' record for ''mail.debserv-.test'' which points to the IP of your system.</li>		<li>Go back to the domain zone overview page. Because we don't currently have an "A" (address) record for ''mail.debserv-.test'' the mail would currently go undelivered. Add an ''A'' record for ''mail.debserv-.test'' which points to the IP of your system.</li>
			<li> To test an ''MX'' record we need to make multiple queries and ask '''nslookup''' or '''dig''' to fist check for MX records for the domain like '''nslookup -type=MX debserv-.test''' or '''dig debserv-.test MX''' which will return the names of the mail servers for that domain. We then need to do a regular '''nslookup''' or '''dig''' on those names to determine what IP addresses those are pointed to. Of course, for mail to actually work we'd also need to insure mail server software is installed and configured on that server as well.</li>
	<li>Again return to the domain zone overview page. We are now going to create a CNAME record. CNAME records are useful as they allow you to create virtual A records (aliases), but point them to another domain or host name instead of to a specific IP address. This allows you to have many hostnames all pointed to the same A record which contains the actual IP address so if the IP address changes you only need to change a single A record and all the hostnames will change. It can also be used to redirect a hostname at one domain to an entirely different domain.</li>		<li>Again return to the domain zone overview page. We are now going to create a CNAME record. CNAME records are useful as they allow you to create virtual A records (aliases), but point them to another domain or host name instead of to a specific IP address. This allows you to have many hostnames all pointed to the same A record which contains the actual IP address so if the IP address changes you only need to change a single A record and all the hostnames will change. It can also be used to redirect a hostname at one domain to an entirely different domain.</li>
	<li>On the ''Edit Master Zone'' page for your domain, click the ''Name Alias'' button. For the ''Name'', enter ''blog'' and for the ''Real Name'', enter your domain ''debserv-*.test.'' but remember to put a period at the end of the domain as this is an ''absolute name''. Press ''create'' to add the record.</li>		<li>On the ''Edit Master Zone'' page for your domain, click the ''Name Alias'' button. For the ''Name'', enter ''blog'' and for the ''Real Name'', enter your domain ''debserv-*.test.'' but remember to put a period at the end of the domain as this is an ''absolute name''. Press ''create'' to add the record.</li>
Line 79:		Line 80:
	</ol>		</ol>
	== Adding a AAAA record ==		== Adding a AAAA record ==
	# Now we are going to add an AAAA (IPv6 host) record to our domain. To do this, we will first need to make sure that IPv6 networking is setup in our virtual machine.		<ol>
	~~# In putty, using your favorite text editor, open up /etc/network/interfaces. We are going~~ to ~~enable~~ IPv6 ~~autoconfiguration to make sure that IPv6 is running~~ on ~~our VM. Add "iface eth0 inet6 auto" to~~ the ~~end if the eth0 configuration to do this if it's not already there~~. ~~Your interface~~ should ~~now look similar to this~~:		<li> Now we are going to add an ''AAAA'' (IPv6 host) record to our domain. To do this, we will first need to make sure that IPv6 networking is setup in our virtual machine.</li>
	~~<pre>auto eth0~~		<li> Use '''ip address show''' to check the ''inet6'' address (IPv6 Address) on the primary network interface. You should have an address starting with ''2607:f930:1c00:50:''. If you do not please check with your instructor. You will need to write down or remember this full address as we will use it in Webmin to create our AAAA record.</li>
	~~iface eth0 inet static~~		<li> Back in Webmin, under the ''BIND DNS Server'' tab, select your ''debserv-*.test'' domain from the bottom and then click the ''IPv6 Address'' button. For the name, enter ''@'' and for the ''address'' enter your IPv6 address WITHOUT the subnet prefix (No /64 on the end). It should look similar to this: ''2607:f930:1c00:50:xxxx:xxxx:xxxx:xxxx''.</li>
	~~address 172.17.~~50.~~xxx~~		<li>When done click ''create''. Remember to click the ''apply configuration'' link in the top right to apply the changes. In order to verify the AAAA record is working we need to modify the '''nslookup''' or '''dig''' command to check for AAAA records instead of the default of A records. Try '''nslookup -type=AAAA debserv-.test''' and '''dig debserv-.test AAAA''' to see the output from AAAA records.
	~~netmask 255~~.~~255.255.0~~		<li>Congratulations, you have now setup a dual-stack DNS records for your Debian server. This means your server is accessible from both IPv4 and IPv6 at the same name because both the A and AAAA records we created have the same host name).</li>
	~~gateway 172.17.50.1~~		</ol>
	~~dns-nameservers 127.0.0.1~~
	~~iface eth0 inet6 auto</pre>~~
	~~# Afterwords, restart the eth0 interface by using "ifdown eth0 && ifup eth0". Remember that you~~ need to ~~run both of these commands (hint there are two commands on~~ this ~~line) as root otherwise it will not work.~~
	~~# Now use ifconfig to find your IPv6~~ address~~. Remember this~~ as we will use it in ~~webmin~~ to create our AAAA record.
	# Back in ~~webmin~~, under ~~servers and~~ BIND DNS Server, select your debserv-*.test domain from the bottom and then click the IPv6 Address button. For the name, enter @ and for the address enter your IPv6 address WITHOUT the subnet prefix. It should look similar to this. 2607:f930:1c00:50:xxxx:xxxx:xxxx:xxxx
	# When done ~~press~~ create. Remember to ~~press~~ the apply configuration ~~button~~ in the top right to ~~make these~~ changes ~~applied~~. ~~Now use~~ nslookup to ~~lookup your domain,~~ and ~~notice how you now have a IPv6 and IPv4 record for your domain~~.
	# Congratulations, you have now setup a dual-stack DNS server ~~for~~ your ~~debian~~ server.

	== Adding a Delegated Domain ==		== Adding a Delegated Domain ==
	~~# Now~~ we are going to add another domain to the system, but this domain is a delegated domain. Luckily we can add this to BIND the same way we added our ~~first~~ domain.		<ol>
	~~# So in~~ Webmin, go to Servers, then BIND DNS Server. ~~Then under~~ Existing DNS Zones~~, Click~~ on Create Master Zone and use the following settings:		<li>The problem with the name we have been using so far is that it only works on the DNS server itself. This is because we didn't purchase the name and so no other nameservers know to send requests for it to our server. Normally if you purchase a domain or someone else gives you control of a subdomain it is ''delegated'' to your server meaning that other DNS servers will query your server for addresses related to that name. In order to practice this we are going to add another domain to the system, but this domain will be a delegated domain which is a subdomain of ''itc2480.campus.ihitc.net''. Luckily we can add this to BIND the same way we added our original domain.</li>
			<li>In Webmin, go to ''Servers'', then ''BIND DNS Server''. Under ''Existing DNS Zones'' click on ''Create Master Zone'' and use the following settings:
	<pre>Zone type: Forward (Names to Addresses)		<pre>Zone type: Forward (Names to Addresses)
	Domain name / Network: *.itc2480.campus.ihitc.net		Domain name / Network: *.itc2480.campus.ihitc.net
Line 102:		Line 97:
	Master server: *.itc2480.campus.ihitc.net.		Master server: *.itc2480.campus.ihitc.net.
	Email address: root@ *.itc2480.campus.ihitc.net</pre>		Email address: root@ *.itc2480.campus.ihitc.net</pre>
	* '''NOTE: the * stands for your ~~hostname~~ letter, the same as you used for the ~~other~~ domain we created.'''		* '''NOTE: the * stands for your System ID letter, the same as you used for the previous domain we created.'''</li>
	~~# Now using~~ webmin, create an A record for @ the same way as we did for the last domain. If you need help with this step, you can review the process we did earlier. Make sure to apply your changes after adding the record.		<li> Using webmin, create an ''A'' record for ''@'' the same way as we did for the last domain. If you need help with this step, you can review the process we did earlier. Make sure to apply your changes after adding the record.</li>
	#* Test that the record and delegation are working correctly. ~~From~~ your host computer ~~try doing an~~ nslookup on *.itc2480.campus.ihitc.net ~~does~~ the correct address come back?		<li>Test that the record and delegation are working correctly. This time you should be able to check from your host computer too! Windows does not include the '''dig''' command so you'll need to use '''nslookup''' on ''.itc2480.campus.ihitc.net'' (replace the with your System ID). Does the correct address come back?</li>
	~~# Create an MX record for the domain which directs mail for your delegated domain to your system as well.~~		<li> Test your setup using a web browser on your local computer, can you access your webserver by going to http://.itc2480.campus.ihitc.net (where is your hostname letter)?</li>
	# Test your setup using a web browser on your local computer, can you access your webserver by going to http://.itc2480.campus.ihitc.net (where is your hostname letter)?		<li>Create an ''MX'' record for the domain which directs mail for your delegated domain to your system as well just like we did with the test domain (this will involve creating another A record for ''mail.*.itc2480.campus.ihitc.net'' as well).</li>
	# Create a CNAME record for the blog just like in the previous example and create a new Apache virtual server just like in the previous example as well		<li>Test that the MX record and associated A record are working correctly. This time you should be able to check from your host computer too! Windows does not include the '''dig''' command so you'll need to use '''nslookup'''. Does the correct mail server name and address come back?</li>
	# Test your setup using a web browser on your local computer, can you access your blog directly by going to http://blog..itc2480.campus.ihitc.net (where is your hostname letter)?		<li>Create a ''CNAME'' record for the blog just like in the previous example (''blog.*.itc2480.campus.ihitc.net''' though) and create a new Apache virtual server just like in the previous example as well.</li>
			<li>Test your setup using a web browser on your local computer, can you access your blog directly by going to http://blog..itc2480.campus.ihitc.net (where is your hostname letter)?</li>
			</ol>

	== Manually editing a zone file ==		== Manually editing a zone file ==

BenFranske at 22:27, 23 February 2018

2018-02-23T22:27:31Z

← Older revision		Revision as of 22:27, 23 February 2018
Line 27:		Line 27:
	</pre>		</pre>
	* Notice how it shows it is using 127.0.0.1 as the server. If you do not see this, then your interface file or resolv.conf file is not set to use the local machine for DNS lookups. Note also that the IP address returned for this domain may vary from the one shown in the output above.</li>		* Notice how it shows it is using 127.0.0.1 as the server. If you do not see this, then your interface file or resolv.conf file is not set to use the local machine for DNS lookups. Note also that the IP address returned for this domain may vary from the one shown in the output above.</li>
	<li>Experiment using the '''dig''' utility to check DNS name resolution which can provide more detailed output than '''nslookup'''. Run ''dig inverhills.edu''' and see if you can find where the IP address for the domain is reported in the output as well as where the server IP address is reported in the output.</li>		<li>Experiment using the '''dig''' utility to check DNS name resolution which can provide more detailed output than '''nslookup'''. Run '''dig inverhills.edu''' and see if you can find where the IP address for the domain is reported in the output as well as where the server IP address is reported in the output.</li>
	</ol>		</ol>
	== Create a Domain using Webmin ==		== Create a Domain using Webmin ==
Line 33:		Line 33:
	<li>Now we are going to use Webmin to create a few different type of domain records and have our system serve as a DNS server for a domain. We will utilize A (Host), AAAA (IPv6 host), MX (Mail Exchange), and CNAME (Canonical Name) records.</li>		<li>Now we are going to use Webmin to create a few different type of domain records and have our system serve as a DNS server for a domain. We will utilize A (Host), AAAA (IPv6 host), MX (Mail Exchange), and CNAME (Canonical Name) records.</li>
	<li>Open up your Webmin panel and sign in. Now that we have BIND installed, you will need to click the Refresh Modules option on the left sidebar to have Webmin recheck the system for installed packages and services so that it will show up as an option in the ''Servers'' tab.</li>		<li>Open up your Webmin panel and sign in. Now that we have BIND installed, you will need to click the Refresh Modules option on the left sidebar to have Webmin recheck the system for installed packages and services so that it will show up as an option in the ''Servers'' tab.</li>
	~~# Now under~~ the ''Servers'' tab, open up ''BIND DNS Server'', under ''Existing DNS Zones'' click ''Create master zone''. From here we will create a new domain name for our server to respond to DNS queries for.</li>		<li>Under the ''Servers'' tab, open up ''BIND DNS Server'', under ''Existing DNS Zones'' click ''Create master zone''. From here we will create a new domain name for our server to respond to DNS queries for.</li>
	<li>Use the following options, '''where * is replaced by your System ID''' that was defined in [[Franske ITC-2480 Lab 5\|Lab 5]] (just the letter of your system, for example the domain name would be ''debserv-A.test'' if you had System ID "A").		<li>Use the following options, '''where * is replaced by your System ID''' that was defined in [[Franske ITC-2480 Lab 5\|Lab 5]] (just the letter of your system, for example the domain name would be ''debserv-A.test'' if you had System ID "A").
	<pre>Zone type: Forward (Names to Addresses)		<pre>Zone type: Forward (Names to Addresses)
Line 45:		Line 45:
	* If you have issues looking up the domain, make sure that the system is still using 127.0.0.1 as the DNS server. If not, check your ''/etc/resolv.conf'' file.</li>		* If you have issues looking up the domain, make sure that the system is still using 127.0.0.1 as the DNS server. If not, check your ''/etc/resolv.conf'' file.</li>
	</ol>		</ol>
	== ~~Adding additional record types~~ ==		== Additional DNS Record Types ==
	# Now we are going to add a few more record types to our Domain. This will include a MX (Mail Exchange) and CNAME (Canonical Name) record.		<ol>
	# We will start with the MX record. MX records are used by email servers to look up where to forward email for a specific domain.		<li>Now we are going to add a few more record types to our Domain. This will include an ''MX'' (Mail Exchange) and ''CNAME'' (Canonical Name) record.</li>
	~~# So to~~ create a MX record we will use Webmin again. In Webmin on the BIND DNS Server page, click the domain on the bottom named debserv-.test and then click the Mail Server button. Under name, enter @ again, and for mail server enter mail.debserv-.test. (with the ~~final~~ period). ~~Now for~~ Priority, enter 10. The Priority entry allows people to define more than 1 MX record for a ~~domain~~, and the ~~Priority defines~~ which ~~one should be used before~~ the ~~rest~~.		<li>We will start with the MX record. MX records are used by email servers to look up where to forward email for a specific domain.</li>
	~~# Now go~~ back to the domain zone overview page. Add an A record for mail.debserv-*.test which ~~uses~~ the IP of your system.		</li>To create a MX record we will use Webmin again. In Webmin on the ''BIND DNS Server'' page, click the domain on the bottom named ''debserv-.test'' and then click the ''Mail Server'' button. Under ''name'', enter ''@'' again, and for ''mail server'' enter ''mail.debserv-.test.'' (with the period at the end). For ''Priority'', enter ''10''.
	~~# Now go back~~ to the domain zone overview page. We are now going to create a CNAME record. CNAME records are useful as they allow you to create virtual A records, but point them to a domain name instead of a ~~host~~. This ~~is most helpful in situations where~~ you have ~~a dynamic~~ IP address on a ~~system that always has~~ a ~~common DNS name~~.		* This entry has said we want other servers trying to send mail to ''users@debserv-.test'' to actually send it to the server at ''mail.debserv-.test'' which allows us to use a different server for email than we use fore web serving, etc.
	~~# Now on~~ the Edit Master Zone page for your domain, click the Name Alias button. For the Name, enter "blog" and for the Real Name, enter your domain "debserv-*.test." but remember to put a period at the end of the domain as this is an absolute name. ~~Then press~~ create to add the record.		* The Priority entry allows people to define more than 1 MX record for a name, and the order which the sending service will try to use for contacting the various mail servers at your domain.</li>
	~~# Now press~~ the Apply Configuration ~~option in~~ the top right of the page again. This will apply the records you have created. Now back in ~~putty~~, run "nslookup blog.debserv-*.test". You should get a response similar to:		<li>Go back to the domain zone overview page. Because we don't currently have an "A" (address) record for ''mail.debserv-.test'' the mail would currently go undelivered. Add an ''A'' record for ''mail.debserv-.test'' which points to the IP of your system.</li>
			<li>Again return to the domain zone overview page. We are now going to create a CNAME record. CNAME records are useful as they allow you to create virtual A records (aliases), but point them to another domain or host name instead of to a specific IP address. This allows you to have many hostnames all pointed to the same A record which contains the actual IP address so if the IP address changes you only need to change a single A record and all the hostnames will change. It can also be used to redirect a hostname at one domain to an entirely different domain.</li>
			<li>On the ''Edit Master Zone'' page for your domain, click the ''Name Alias'' button. For the ''Name'', enter ''blog'' and for the ''Real Name'', enter your domain ''debserv-*.test.'' but remember to put a period at the end of the domain as this is an ''absolute name''. Press ''create'' to add the record.</li>
			<li>Click the ''Apply Configuration'' link at the top right of the page again. This will apply the records you have created. Now back in PuTTY, run '''nslookup blog.debserv-*.test''' or the equivalent '''dig''' command. You should get a response similar to:
	<pre>Server: 127.0.0.1		<pre>Server: 127.0.0.1
	Address: 127.0.0.1#53		Address: 127.0.0.1#53
Line 59:		Line 62:
	Name: debserv-*.test		Name: debserv-*.test
	Address: 172.17.50.XXX		Address: 172.17.50.XXX
	</pre>		</pre></li>
	~~# Now~~ we ~~are going~~ to create a virtual web ~~host~~ in ~~apache~~ that listens for the domain blog.debserv-*.test, and then forwards you directly to your blog folder.		<li>One thing we can use CNAMEs for is to create virtual web hosts in Apache that listens for the domain blog.debserv-*.test, and then forwards you directly to your blog folder instead of to our main web page. </li>
	# In Webmin under the ~~servers~~ tab, select Apache Webserver. Then on the top, click the Create virtual host button and use the following ~~Configuration~~:		<li>In Webmin under the ''Servers'' tab, select ''Apache Webserver''. Then on the top, click the ''Create virtual host'' button and use the following configuration:
	<pre>Handle Connections to Address: any address		<pre>Handle Connections to Address: any address
	Port: 80		Port: 80
Line 69:		Line 72:
	Copy directives from: nowhere		Copy directives from: nowhere
	</pre>		</pre>
	# When done, press Create Now. When you are back at the Apache Webserver page, then click Apply Changes in the top right.		When done, press ''Create Now''.
	# Now in a SSH session, open up your favorite command line web browser like ~~w3m~~ and visit blog.debserv-*.test. Notice how you are now visiting the blog directly, instead of your modified index.html file. This is because we setup a virtual host in ~~apache~~ that listens for requests ~~directly from~~ the CNAME we created.		<li> When you are back at the ''Apache Webserver'' page, then click ''Apply Changes'' in the top right.</li>
	# Congrats, at this point you have a basic domain working with a MX, CNAME, and A record.		<li>Now in a SSH session, open up your favorite command line web browser like '''links''' and visit ''blog.debserv-*.test''. Notice how you are now visiting the blog directly, instead of your modified index.html file. This is because we setup a virtual host in Apache that listens for requests to the CNAME we created and points to the document root where the Wordpress software is installed.
			* Note that you will not be able to use this URL to access the blog from your local PC yet because your local PC isn't using your Linux server as it's DNS server and the .test domain isn't registered to your DNS server.</li>
			<li>Congrats, at this point you have a basic domain working with a MX, CNAME, and A record.</li>
			</ol>
	== Adding a AAAA record ==		== Adding a AAAA record ==
	# Now we are going to add an AAAA (IPv6 host) record to our domain. To do this, we will first need to make sure that IPv6 networking is setup in our virtual machine.		# Now we are going to add an AAAA (IPv6 host) record to our domain. To do this, we will first need to make sure that IPv6 networking is setup in our virtual machine.