<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Tuts4Tech &#187; DNS</title>
	<atom:link href="http://tuts4tech.net/tag/dns/feed/" rel="self" type="application/rss+xml" />
	<link>http://tuts4tech.net</link>
	<description>Tech Tutorials</description>
	<lastBuildDate>Sun, 18 Jul 2010 01:41:08 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>How to flush your dns cache</title>
		<link>http://tuts4tech.net/2009/08/08/how-to-flush-your-dns-cache/</link>
		<comments>http://tuts4tech.net/2009/08/08/how-to-flush-your-dns-cache/#comments</comments>
		<pubDate>Sat, 08 Aug 2009 02:01:51 +0000</pubDate>
		<dc:creator>Duffy</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[OSX]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[cache]]></category>
		<category><![CDATA[DNS]]></category>
		<category><![CDATA[domain]]></category>
		<category><![CDATA[internet]]></category>
		<category><![CDATA[nameserver]]></category>

		<guid isPermaLink="false">http://tuts4tech.net/?p=539</guid>
		<description><![CDATA[Windows Firstly open a cmd box by going to start > run > cmd Then flush your dns by running the following: ipconfig /flushdns OSX Open your terminal Run the following command: dscacheutil -flushcache Linux Just run the following: /etc/init.d/nscd restart]]></description>
			<content:encoded><![CDATA[<h3>Windows</h3>
<p></p>
<ol>
<li>Firstly open a cmd box by going to start > run > cmd</li>
<li>Then flush your dns by running the following:
<pre class="brush: plain;">ipconfig /flushdns</pre>
</li>
</ol>
<p></p>
<h3>OSX</h3>
<p></p>
<ol>
<li>Open your terminal</li>
<li>Run the following command:
<pre class="brush: plain;">dscacheutil -flushcache</pre>
</li>
</ol>
<p></p>
<h3>Linux</h3>
<p></p>
<ol>
<li>Just run the following:
<pre class="brush: plain;">/etc/init.d/nscd restart</pre>
</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://tuts4tech.net/2009/08/08/how-to-flush-your-dns-cache/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Setting up a DNS Server for your LAN Network</title>
		<link>http://tuts4tech.net/2009/05/08/setting-up-a-dns-server-for-your-lan-network/</link>
		<comments>http://tuts4tech.net/2009/05/08/setting-up-a-dns-server-for-your-lan-network/#comments</comments>
		<pubDate>Fri, 08 May 2009 10:49:58 +0000</pubDate>
		<dc:creator>Duffy</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Debian]]></category>
		<category><![CDATA[DNS]]></category>
		<category><![CDATA[domain]]></category>
		<category><![CDATA[hostname]]></category>
		<category><![CDATA[lan]]></category>
		<category><![CDATA[networking]]></category>
		<category><![CDATA[resolve]]></category>

		<guid isPermaLink="false">http://tuts4tech.co.cc/?p=186</guid>
		<description><![CDATA[This tutorial will show you how to configure bind9 on debian to be a dns server for your LAN network. Install bind9 and some DNS utilities apt-get install bind9 dnsutils Set your systems hostname echo &#34;server.home.local&#34; &#62; /etc/hostname then edit /etc/hosts so it looks like this 127.0.0.1 localhost.localdomain localhost 192.168.1.2 server.home.local server # The following [...]]]></description>
			<content:encoded><![CDATA[<p>This tutorial will show you how to configure bind9 on debian to be a dns server for your LAN network.</p>
<ol>
<li>Install bind9 and some DNS utilities
<pre class="brush: plain;">apt-get install bind9 dnsutils</pre>
</li>
<li>Set your systems hostname
<pre class="brush: plain;">echo &quot;server.home.local&quot; &gt; /etc/hostname </pre>
<p>then edit /etc/hosts so it looks like this
<pre class="brush: plain;">127.0.0.1       localhost.localdomain   localhost
192.168.1.2    server.home.local        server
# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts</pre>
</li>
<li>change you DNS servers by editing /etc/resolv.conf
<pre class="brush: plain;">nano /etc/resolv.conf</pre>
<p>it should look something like this:
<pre class="brush: plain;">
search home.local
nameserver 192.168.1.2</pre>
</li>
<li>
<h4>Creating a Zone</h4>
</li>
</ol>
<p><span id="more-186"></span>
<ol>
<li>The zone files are the most important part of the BIND system. They hold all the information as to what hostname goes to an IP. to get started edit /etc/bind/named.conf.local
<pre class="brush: plain;">nano /etc/bind/named.conf.local</pre>
<p>and then add the following:
<pre class="brush: plain;">zone &quot;home.local&quot; {
        type master;
        file &quot;home.local&quot;;
};

zone &quot;1.168.192.in-addr.arpa&quot; {
        type master;
        file &quot;192.168.1&quot;;
};</pre>
</li>
<li>Now we need to create the zone file in /var/cache/bind/home.local
<pre class="brush: plain;">nano /var/cache/bind/home.local</pre>
<p> and add the following:
<pre class="brush: plain;">$TTL 604800
@ IN SOA server.home.local. sysadmin.home.local. (
                2008080101      ;serial
                04800           ;refresh
                86400           ;retry
                2419200         ;expire
                604800          ;negative cache TTL
                )
@       IN      NS      server.home.local.
@       IN      A       192.168.1.2
@       IN      MX      10      server.home.local.
server  IN      A       192.168.1.2
www     IN      CNAME   server
desktop	IN	A	192.168.1.3
printer	IN	A	192.168.2.4
laptop	IN	A	192.168.2.5</pre>
</li>
<p>Now we need to create the reverse DNS zone file to do so we need to create /var/cache/bind/192.168.1
<pre class="brush: plain;">nano /var/cache/bind/192.168.1</pre>
<p> and add the following:
<pre class="brush: plain;">$TTL 604800
@ IN SOA server.home.local. sysadmin.home.local. (
                2008080101      ;serial
                604800          ;refresh
                86400           ;retry
                2419200         ;expire
                604800          ;negative cache TTL
                )
@       IN      NS      server.home.local.
@       IN      A       192.168.1.2
2	IN	PTR	server.home.local.
3	IN	PTR	desktop.home.local.
4	IN	PTR	printer.home.local.
5	IN	PTR	laptop.home.local.</pre>
</ol>
<li>We now need to set DNS servers to forward to so edit /etc/bind/named.conf.options
<pre class="brush: plain;">nano /etc/bind/named.conf.options</pre>
<p>and add the following
<pre class="brush: plain;">forwarders {
                208.67.222.222; // your isps dns server
                208.67.220.220; // your isps dns server
        };</pre>
</li>
<li>Now we need to restart bind9 and test it
<pre class="brush: plain;">/etc/init.d/bind9 restart</pre>
<p>
<pre class="brush: plain;">dig home.local</pre>
<p>you should see the following
<pre class="brush: plain;">; &lt; &lt;&gt;&gt; DiG 9.3.4 &lt; &lt;&gt;&gt; home.local
;; global options:  printcmd
;; Got answer:
;; -&gt;&gt;HEADER&lt; &lt;- opcode: QUERY, status: NOERROR, id: 54950
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1

;; QUESTION SECTION:
;home.local.                    IN      A

;; ANSWER SECTION:
home.local.             64800   IN      A       192.168.1.2

;; AUTHORITY SECTION:
home.local.             64800   IN      NS      server.home.local.

;; ADDITIONAL SECTION:
server.home.local.        64800   IN      A       192.168.1.2

;; Query time: 1 msec
;; SERVER: 192.168.1.2#53(192.168.1.2)
;; WHEN: Tue Aug  5 09:33:40 2008
;; MSG SIZE  rcvd: 79</pre>
</pre>
</li>
<li>Configure all computers in your network to use 192.168.1.2 as there dns server and you should be good to go</li>
]]></content:encoded>
			<wfw:commentRss>http://tuts4tech.net/2009/05/08/setting-up-a-dns-server-for-your-lan-network/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Finding out the subdomains of a domain</title>
		<link>http://tuts4tech.net/2009/04/02/finding-out-the-subdomains-of-a-domain/</link>
		<comments>http://tuts4tech.net/2009/04/02/finding-out-the-subdomains-of-a-domain/#comments</comments>
		<pubDate>Thu, 02 Apr 2009 12:14:05 +0000</pubDate>
		<dc:creator>Duffy</dc:creator>
				<category><![CDATA[Misc]]></category>
		<category><![CDATA[bind9]]></category>
		<category><![CDATA[Debian]]></category>
		<category><![CDATA[dig]]></category>
		<category><![CDATA[DNS]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://duffys-place.co.cc/?p=39</guid>
		<description><![CDATA[1. First off you need to get a program called dig for debian based Operating systems you can do apt-get install dnsutils a windows version can be downloaded from here 2. Find out the name servers of the domain this can be done by typing dig ns &#60;domain&#62; 3. Now you query the Nameserver to [...]]]></description>
			<content:encoded><![CDATA[<p>1. First off you need to get a program called dig<br />
for debian based Operating systems you can do
<pre class="brush: plain;">apt-get install dnsutils</pre>
<p>a windows version can be downloaded from <a href="http://members.shaw.ca/nicholas.fong/dig/">here</a></p>
<p>2. Find  out the name servers of the domain this can be done by typing</p>
<pre class="brush: plain;">dig ns &lt;domain&gt;</pre>
<p>3. Now you query the Nameserver to output the subdomains</p>
<pre class="brush: plain;">dig @&lt;nameserver&gt; &lt;domain&gt; axfr</pre>
<p>4. You should now have a listing of all the subdomains :)</p>
<p>Example:</p>
<pre class="brush: plain;">root@duffys-place:~# dig ns duffys-place.co.cc

; &lt; &lt;&gt;&gt; DiG 9.5.1-P1 &lt; &lt;&gt;&gt; ns duffys-place.co.cc
;; global options:  printcmd
;; Got answer:
;; -&gt;&gt;HEADER&lt; &lt;- opcode: QUERY, status: NOERROR, id: 48938
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;duffys-place.co.cc.            IN      NS

;; ANSWER SECTION:
duffys-place.co.cc.     43180   IN      NS      ns3.co.cc.

;; Query time: 23 msec
;; SERVER: 212.113.0.3#53(212.113.0.3)
;; WHEN: Thu Apr  2 13:12:59 2009
;; MSG SIZE  rcvd: 54

root@duffys-place:~# dig @ns3.co.cc duffys-place.co.cc axfr

; &lt;&lt;&gt;&gt; DiG 9.5.1-P1 &lt; &lt;&gt;&gt; @ns3.co.cc duffys-place.co.cc axfr
; (1 server found)
;; global options:  printcmd
duffys-place.co.cc.     86400   IN      SOA     ns.duffys-place.co.cc. root.duffys-place.ns.co.cc. 2009030300 28800 7200 604800 3600
duffys-place.co.cc.     86400   IN      NS      ns3.co.cc.
duffys-place.co.cc.     86400   IN      A       88.151.87.96
duffys-place.co.cc.     86400   IN      MX      10 mail1.duffys-place.co.cc.
files.duffys-place.co.cc. 3600  IN      CNAME   cid-d037be1f66fbe46e.skydrive.live.com.
home.duffys-place.co.cc. 86400  IN      A       88.151.87.116
mail.duffys-place.co.cc. 86400  IN      CNAME   ghs.google.com.
mail1.duffys-place.co.cc. 86400 IN      CNAME   aspmx.l.google.com.
paste.duffys-place.co.cc. 86400 IN      CNAME   duffys-place.co.cc.
shane.duffys-place.co.cc. 86400 IN      CNAME   duffys-place.co.cc.
sms.duffys-place.co.cc. 86400   IN      CNAME   duffys-place.co.cc.
usermin.duffys-place.co.cc. 86400 IN    A       88.151.87.98
webmin.duffys-place.co.cc. 86400 IN     A       88.151.87.97
www.duffys-place.co.cc. 86400   IN      CNAME   duffys-place.co.cc.
duffys-place.co.cc.     86400   IN      SOA     ns.duffys-place.co.cc. root.duffys-place.ns.co.cc. 2009030300 28800 7200 604800 3600
;; Query time: 308 msec
;; SERVER: 118.219.232.169#53(118.219.232.169)
;; WHEN: Thu Apr  2 13:13:06 2009
;; XFR size: 15 records (messages 1, bytes 442)</pre>
<p><strong>Please Note This Will Only Work On Some Nameservers</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://tuts4tech.net/2009/04/02/finding-out-the-subdomains-of-a-domain/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
