Franske ITC-2480 Lab 9 - Revision history

BenFranske: /* Adding a AAAA record */

2014-03-24T21:26:21Z

Adding a AAAA record

← Older revision		Revision as of 21:26, 24 March 2014
Line 70:		Line 70:
	== 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.
	# In putty, using your favorite text editor, open up /etc/network/interfaces. We are going to enable IPv6 ~~over DHCP~~ to make sure that IPv6 is running on our VM. Add "iface eth0 inet6 ~~dhcp~~" to the end if the eth0 configuration to do this. Your interface should now look similar to this:		# 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. Your interface should now look similar to this:
	<pre>auto eth0		<pre>auto eth0
	iface eth0 inet static		iface eth0 inet static

BenFranske: /* Adding a AAAA record */

2014-03-24T21:25:52Z

Adding a AAAA record

← Older revision		Revision as of 21:25, 24 March 2014
Line 77:		Line 77:
	gateway 172.17.50.1		gateway 172.17.50.1
	dns-nameservers xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx		dns-nameservers xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx
	iface eth0 inet6 ~~dhcp~~</pre>		iface eth0 inet6 auto</pre>
	# Afterwords, restart the eth0 interface by using "ifdown eth0 && ifup eth0". Remember that you need to run this command as root otherwise it will not work.		# Afterwords, restart the eth0 interface by using "ifdown eth0 && ifup eth0". Remember that you need to run this command 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.		# Now use ifconfig to find your IPv6 address. Remember this as we will use it in webmin to create our AAAA record.

BenFranske: /* Adding a Delegated Domain */

2014-03-20T02:08:53Z

Adding a Delegated Domain

← Older revision		Revision as of 02:08, 20 March 2014
Line 94:		Line 94:
	* NOTE: the * stands for your hostname letter, the same as you used for the other domain we created.		* NOTE: the * stands for your hostname letter, the same as you used for the other domain we created.
	# 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.		# 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.
			# Create an MX record for the domain which directs mail for your delegated domain to your system as well.

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

BenFranske: /* Install BIND & Enable Caching */

2014-03-20T02:07:03Z

Install BIND & Enable Caching

← Older revision		Revision as of 02:07, 20 March 2014
Line 9:		Line 9:
	# Now we will need to enable DNS caching and forwarding on the bind server. This will allow us to use it for DNS resolving locally, as well as speed up frequent DNS requests. To do this, open up /etc/bind/named.conf.options with your favorite text editor.		# Now we will need to enable DNS caching and forwarding on the bind server. This will allow us to use it for DNS resolving locally, as well as speed up frequent DNS requests. To do this, open up /etc/bind/named.conf.options with your favorite text editor.
	# You are now in the local options file for bind. You will need to uncomment out the following lines:		# You are now in the local options file for bind. You will need to uncomment out the following lines:
	<pre># forwarders {		<pre>// forwarders {
	# 0.0.0.0;		// 0.0.0.0;
	# };</pre>		// };</pre>
	* Note that you will need to replace 0.0.0.0 with 172.17.139.10 for outside DNS lookups to function.		* Note that you will need to replace 0.0.0.0 with 172.17.139.10 for outside DNS lookups to function.
	# 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.		# 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.
	# To apply this change, you will need to restart the Bind DNS serice. to do this run "sudo service bind9 restart". This will restart the Bind DNS service.		# To apply this change, you will need to restart the Bind DNS serice. to do this run "sudo service bind9 restart". This will restart the Bind DNS service.
	# Next we will need to change our DNS server set in /etc/network/interfaces so our eth0 interfaces uses our local system for DNS lookups. To do this, open up your interfaces file with your favorite file editor, and change the dns server to 127.0.0.1. ~~Remember~~ to restart your ~~interface eth0~~ to ~~apply~~ the ~~changes~~.		# Next we will need to change our DNS server set in /etc/network/interfaces so our eth0 interfaces uses our local system for DNS lookups. To do this, open up your interfaces file with your favorite file editor, and change the dns server to 127.0.0.1.
			# The change to /etc/network/interfaces will take effect if you restart your system. To avoid doing that you'll want to edit the /etc/resolv.conf file so that it has only one nameserver line with "nameserver 127.0.0.1"
	# To test if its working, run the command "nslookup inverhills.edu". If bind is working, you should now see the following output:		# To test if its working, run the command "nslookup inverhills.edu". If bind is working, you should now see the following output:
	<pre>Server: 127.0.0.1		<pre>Server: 127.0.0.1
Line 24:		Line 25:
	Address: 134.29.183.71		Address: 134.29.183.71
	</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 is not set to use the local machine for DNS lookups.		* 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.

	== Create a Domain using Webmin ==		== Create a Domain using Webmin ==

Riptide wave: /* Adding a AAAA record */

2014-03-19T23:01:58Z

Adding a AAAA record

← Older revision		Revision as of 23:01, 19 March 2014
Line 79:		Line 79:
	# Afterwords, restart the eth0 interface by using "ifdown eth0 && ifup eth0". Remember that you need to run this command as root otherwise it will not work.		# Afterwords, restart the eth0 interface by using "ifdown eth0 && ifup eth0". Remember that you need to run this command 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.		# 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 ~~as well as~~ the subnet prefix. It should look similar to this. 2607:f930:1c00:50:xxxx:xxxx:xxxx:xxxx~~/64~~		# 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.		# 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 not setup a dual-stack DNS server for your debian server.		# Congratulations, you have not setup a dual-stack DNS server for your debian server.

BenFranske at 22:55, 19 March 2014

2014-03-19T22:55:39Z

← Older revision		Revision as of 22:55, 19 March 2014
Line 83:		Line 83:
	# Congratulations, you have not setup a dual-stack DNS server for your debian server.		# Congratulations, you have not setup a dual-stack DNS server for your debian server.

	== Adding a ~~Forwarded~~ Domain ==		== Adding a Delegated Domain ==
	# Now we are going to add another domain to the system, but this domain is a ~~forwarded~~ domain. Luckily we can add this to BIND the same way we added our first 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.
	# 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:		# 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:
	<pre>Zone type: Forward (Names to Addresses)		<pre>Zone type: Forward (Names to Addresses)

Riptide wave: /* Adding a Forwarded Domain */

2014-03-19T02:25:38Z

Adding a Forwarded Domain

← Older revision		Revision as of 02:25, 19 March 2014
Line 84:		Line 84:

	== Adding a Forwarded Domain ==		== Adding a Forwarded Domain ==
			# Now we are going to add another domain to the system, but this domain is a forwarded domain. Luckily we can add this to BIND the same way we added our first domain.
			# 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:
			<pre>Zone type: Forward (Names to Addresses)
			Domain name / Network: *.itc2480.campus.ihitc.net
			Records file: Automatic
			Master server: Leave as your hostname
			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.
			# 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.

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

Riptide wave: /* Adding an AAAA record */

2014-03-18T23:18:06Z

Adding an AAAA record

← Older revision		Revision as of 23:18, 18 March 2014
Line 67:		Line 67:
	# Congrats, at this point you have a basic domain working with a MX, CNAME, and A record.		# Congrats, at this point you have a basic domain working with a MX, CNAME, and A record.

	== Adding an 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.
	# In putty, using your favorite text editor, open up /etc/network/interfaces. We are going to enable IPv6 over DHCP to make sure that IPv6 is running on our VM. Add "iface eth0 inet6 dhcp" to the end if the eth0 configuration to do this. Your interface should now look similar to this:		# In putty, using your favorite text editor, open up /etc/network/interfaces. We are going to enable IPv6 over DHCP to make sure that IPv6 is running on our VM. Add "iface eth0 inet6 dhcp" to the end if the eth0 configuration to do this. Your interface should now look similar to this:

Riptide wave: /* Adding an AAAA record */

2014-03-18T23:16:15Z

Adding an AAAA record

@@ Line 69: / Line 69: @@
 == Adding an 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.
 == Adding a Forwarded Domain ==

Riptide wave at 22:22, 18 March 2014

2014-03-18T22:22:38Z

← Older revision		Revision as of 22:22, 18 March 2014
Line 45:		Line 45:
	# 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 the address enter your VM's static IP address. Now for Priority, enter 1. 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.		# 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 the address enter your VM's static IP address. Now for Priority, enter 1. 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.
	# 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.		# 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.
	# Now on the Edit Master Zone page for your domain, click the Name Alias button. For the Name, enter "~~cname~~" 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.		# 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.
	# 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 ~~cname~~.debserv-*.test". You should get a response similar to:		# 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:
	<pre>Server: 127.0.0.1		<pre>Server: 127.0.0.1
	Address: 127.0.0.1#53		Address: 127.0.0.1#53

	~~cname~~.debserv-.test canonical name = debserv-.test.		blog.debserv-.test canonical name = debserv-.test.
	Name: debserv-*.test		Name: debserv-*.test
	Address: 172.17.50.XXX		Address: 172.17.50.XXX
	</pre>		</pre>
			# 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.
			# 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
			Port: 80
			Document Root: /var/www/blog/
			Server Name: blog.debserv-*.test
			Add virtual server to file: new file under virtual servers directory
			Copy directives from: nowhere
			</pre>
			# When done, press Create Now. When you are back at the Apache Webserver page, then click Apply Changes in the top right.
			# 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.
	# Congrats, at this point you have a basic domain working with a MX, CNAME, and A record.		# Congrats, at this point you have a basic domain working with a MX, CNAME, and A record.

			== Adding an 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.

			== Adding a Forwarded Domain ==

	== 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.		# 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.