<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Don't be THAT guy...  The case of the missing DNS zone</title><link>http://blogs.technet.com/networking/archive/2008/08/08/don-t-be-that-guy-the-case-of-the-missing-dns-zone.aspx</link><description>Introduction to the &amp;#8220;Don&amp;#8217;t be THAT guy&amp;#8221; blog series: I come in to work every day and get calls with these exact scenarios.&amp;#160; Of course, the names have been changed to protect the innocent and to keep the guilty from having to find</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Here&amp;#8217;s a AD DNS Screwup I have seen firsthand | Paul's esoteric meanderings</title><link>http://blogs.technet.com/networking/archive/2008/08/08/don-t-be-that-guy-the-case-of-the-missing-dns-zone.aspx#3103265</link><pubDate>Mon, 11 Aug 2008 06:03:30 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3103265</guid><dc:creator>Here&amp;#8217;s a AD DNS Screwup I have seen firsthand | Paul's esoteric meanderings</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://neuralfibre.com/paul/it/heres-a-ad-dns-screwup-i-have-seen-firsthand"&gt;http://neuralfibre.com/paul/it/heres-a-ad-dns-screwup-i-have-seen-firsthand&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>Don't be THAT guy...  Assault by Security Template</title><link>http://blogs.technet.com/networking/archive/2008/08/08/don-t-be-that-guy-the-case-of-the-missing-dns-zone.aspx#3122513</link><pubDate>Thu, 11 Sep 2008 19:35:25 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3122513</guid><dc:creator>Microsoft Enterprise Networking Team</dc:creator><description>&lt;p&gt;Introduction to the &amp;amp;#8220;Don&amp;amp;#8217;t be THAT guy&amp;amp;#8221; blog: I come in to work every day and get calls&lt;/p&gt;
</description></item><item><title>re: Don't be THAT guy...  The case of the missing DNS zone</title><link>http://blogs.technet.com/networking/archive/2008/08/08/don-t-be-that-guy-the-case-of-the-missing-dns-zone.aspx#3133474</link><pubDate>Tue, 07 Oct 2008 16:06:46 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3133474</guid><dc:creator>hilde</dc:creator><description>&lt;p&gt;Great info - we had a similar event take place when an admin deleted the DNS zone from a DC that was thought to be having repl issues as a 'step' in troubleshooting. &amp;nbsp;Well, it wasn't having repl issues but shortly after his efforts, there were LOTS of issues with repl being just one. &amp;nbsp;we quickly recovered functionality but in the wrong way: we had a lag site DC, made the AD-i zone there a standard pri zone, copied the text file back over the the PDCE and made a 'new' primary zone, based on that file, then converted it to AD-i. &amp;nbsp;In hindsight, the auth restore was the way to go and we encountered issues from this 'fix' for quite some time. &amp;nbsp;Unfortunately, we just didn't think it through while our world was crumbling around us. &amp;nbsp;Keep up the great postings!&lt;/p&gt;
</description></item></channel></rss>