<?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: Windows Server DNS question</title>
	<atom:link href="http://www.cdavis.us/2008/06/20/windows-server-dns-question/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cdavis.us/2008/06/20/windows-server-dns-question/</link>
	<description>Ramblings from someone who really doesn&#039;t have much to say</description>
	<lastBuildDate>Fri, 01 Jul 2011 18:58:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Chad</title>
		<link>http://www.cdavis.us/2008/06/20/windows-server-dns-question/comment-page-1/#comment-15479</link>
		<dc:creator>Chad</dc:creator>
		<pubDate>Tue, 24 Jun 2008 20:10:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.cdavis.us/?p=2411#comment-15479</guid>
		<description>Chad W-

Ended up not having to. Issue was worked around with some static routing in their Cisco.</description>
		<content:encoded><![CDATA[<p>Chad W-</p>
<p>Ended up not having to. Issue was worked around with some static routing in their Cisco.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chad Wollenberg</title>
		<link>http://www.cdavis.us/2008/06/20/windows-server-dns-question/comment-page-1/#comment-15478</link>
		<dc:creator>Chad Wollenberg</dc:creator>
		<pubDate>Tue, 24 Jun 2008 17:45:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.cdavis.us/?p=2411#comment-15478</guid>
		<description>Hey did you ever figure this out?</description>
		<content:encoded><![CDATA[<p>Hey did you ever figure this out?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chad Wollenberg</title>
		<link>http://www.cdavis.us/2008/06/20/windows-server-dns-question/comment-page-1/#comment-15474</link>
		<dc:creator>Chad Wollenberg</dc:creator>
		<pubDate>Fri, 20 Jun 2008 17:30:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.cdavis.us/?p=2411#comment-15474</guid>
		<description>I tend to think this is not possible, because as soon as you enter the dns into the windows server, your clients are going to be looking at that server to resolve ALL records for that domain. I&#039;ve run into the problem before and never found a solution, other then relocating your dns server into a dmz outside of the internal network.</description>
		<content:encoded><![CDATA[<p>I tend to think this is not possible, because as soon as you enter the dns into the windows server, your clients are going to be looking at that server to resolve ALL records for that domain. I&#8217;ve run into the problem before and never found a solution, other then relocating your dns server into a dmz outside of the internal network.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chad</title>
		<link>http://www.cdavis.us/2008/06/20/windows-server-dns-question/comment-page-1/#comment-15473</link>
		<dc:creator>Chad</dc:creator>
		<pubDate>Fri, 20 Jun 2008 16:59:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.cdavis.us/?p=2411#comment-15473</guid>
		<description>As soon as I added the zone, no one could get to any of the domains they needed to. I had to delete the zone.</description>
		<content:encoded><![CDATA[<p>As soon as I added the zone, no one could get to any of the domains they needed to. I had to delete the zone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chad</title>
		<link>http://www.cdavis.us/2008/06/20/windows-server-dns-question/comment-page-1/#comment-15472</link>
		<dc:creator>Chad</dc:creator>
		<pubDate>Fri, 20 Jun 2008 16:22:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.cdavis.us/?p=2411#comment-15472</guid>
		<description>Thanks Andy! That&#039;s what I figured. I didn&#039;t want to add a DNS zone for this domain as I didn&#039;t want to break any current connectivity to it. This client spends 95% of it&#039;s day attached to their services.</description>
		<content:encoded><![CDATA[<p>Thanks Andy! That&#8217;s what I figured. I didn&#8217;t want to add a DNS zone for this domain as I didn&#8217;t want to break any current connectivity to it. This client spends 95% of it&#8217;s day attached to their services.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://www.cdavis.us/2008/06/20/windows-server-dns-question/comment-page-1/#comment-15471</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Fri, 20 Jun 2008 15:56:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.cdavis.us/?p=2411#comment-15471</guid>
		<description>Of course you can - depending on the dns server, you may just be able to put the ip address in your hosts file on the server. I think this is what I did to block myspace.com - added the entries to our dns server. Alternatively just create a new dns zone for the domain - as long as forwarding is on, the rest of the traffic should get forwarded out.
It gets more difficult if you want to transfer www.notourdomain.com/inside leaving other subdirectories intact though...</description>
		<content:encoded><![CDATA[<p>Of course you can &#8211; depending on the dns server, you may just be able to put the ip address in your hosts file on the server. I think this is what I did to block myspace.com &#8211; added the entries to our dns server. Alternatively just create a new dns zone for the domain &#8211; as long as forwarding is on, the rest of the traffic should get forwarded out.<br />
It gets more difficult if you want to transfer <a href="http://www.notourdomain.com/inside" rel="nofollow">http://www.notourdomain.com/inside</a> leaving other subdirectories intact though&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

