<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Dig All Pointings of a Zone File</title>
	<atom:link href="http://www.technicalguy.org/2010/01/12/dig-all-pointings-of-a-zone-file/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.technicalguy.org/2010/01/12/dig-all-pointings-of-a-zone-file/</link>
	<description>Technical Stuff is boring but Technical Guy is funny</description>
	<lastBuildDate>Fri, 20 Jan 2012 08:42:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: gavin</title>
		<link>http://www.technicalguy.org/2010/01/12/dig-all-pointings-of-a-zone-file/comment-page-1/#comment-818</link>
		<dc:creator>gavin</dc:creator>
		<pubDate>Mon, 17 Jan 2011 20:45:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.technicalguy.org/?p=153#comment-818</guid>
		<description>Thanks for the info.

What if the nameserver disallows this dig?  Is there a backup plan for determining all zone records?

Here is an example of what I mean by the NS disallowing the dig:


gavin@ubuntu:~/Desktop$ dig google.com NS

; &lt;&gt; DiG 9.6.1-P2 &lt;&gt; google.com NS
;; global options: +cmd
;; Got answer:
;; -&gt;&gt;HEADER&lt;&lt;- opcode: QUERY, status: NOERROR, id: 50018
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;google.com.			IN	NS

;; ANSWER SECTION:
google.com.		5	IN	NS	ns4.google.com.
google.com.		5	IN	NS	ns1.google.com.
google.com.		5	IN	NS	ns3.google.com.
google.com.		5	IN	NS	ns2.google.com.

;; Query time: 35 msec
;; SERVER: 192.168.242.2#53(192.168.242.2)
;; WHEN: Mon Jan 17 12:43:36 2011
;; MSG SIZE  rcvd: 100

gavin@ubuntu:~/Desktop$ dig @ns1.google.com google.com AXFR

; &lt;&gt; DiG 9.6.1-P2 &lt;&gt; @ns1.google.com google.com AXFR
; (1 server found)
;; global options: +cmd
; Transfer failed.</description>
		<content:encoded><![CDATA[<p>Thanks for the info.</p>
<p>What if the nameserver disallows this dig?  Is there a backup plan for determining all zone records?</p>
<p>Here is an example of what I mean by the NS disallowing the dig:</p>
<p>gavin@ubuntu:~/Desktop$ dig google.com NS</p>
<p>; &lt;&gt; DiG 9.6.1-P2 &lt;&gt; google.com NS<br />
;; global options: +cmd<br />
;; Got answer:<br />
;; -&gt;&gt;HEADER&lt;&lt;- opcode: QUERY, status: NOERROR, id: 50018<br />
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0</p>
<p>;; QUESTION SECTION:<br />
;google.com.			IN	NS</p>
<p>;; ANSWER SECTION:<br />
google.com.		5	IN	NS	ns4.google.com.<br />
google.com.		5	IN	NS	ns1.google.com.<br />
google.com.		5	IN	NS	ns3.google.com.<br />
google.com.		5	IN	NS	ns2.google.com.</p>
<p>;; Query time: 35 msec<br />
;; SERVER: 192.168.242.2#53(192.168.242.2)<br />
;; WHEN: Mon Jan 17 12:43:36 2011<br />
;; MSG SIZE  rcvd: 100</p>
<p>gavin@ubuntu:~/Desktop$ dig @ns1.google.com google.com AXFR</p>
<p>; &lt;&gt; DiG 9.6.1-P2 &lt;&gt; @ns1.google.com google.com AXFR<br />
; (1 server found)<br />
;; global options: +cmd<br />
; Transfer failed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Solving Spam Problem &#8211; The Malaysia Email Hosting Blog</title>
		<link>http://www.technicalguy.org/2010/01/12/dig-all-pointings-of-a-zone-file/comment-page-1/#comment-724</link>
		<dc:creator>Solving Spam Problem &#8211; The Malaysia Email Hosting Blog</dc:creator>
		<pubDate>Mon, 08 Feb 2010 09:32:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.technicalguy.org/?p=153#comment-724</guid>
		<description>[...] to &#8216;Dig All Pointings of a Zone File&#8216;. I managed to list out the list of pointing for abc.com. We discover xyz.abc.com is not [...]</description>
		<content:encoded><![CDATA[<p>[...] to &#8216;Dig All Pointings of a Zone File&#8216;. I managed to list out the list of pointing for abc.com. We discover xyz.abc.com is not [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

