<?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>Outsourced Clue &#187; Troubleshooting</title>
	<atom:link href="http://outsourcedclue.com/category/troubleshooting/feed/" rel="self" type="application/rss+xml" />
	<link>http://outsourcedclue.com</link>
	<description>Providing big company technology recommendations to the masses</description>
	<lastBuildDate>Thu, 11 Jun 2009 21:05:44 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>SOLVED: Problems with Safari 4, Nginx and Connections being reset</title>
		<link>http://outsourcedclue.com/2009/04/16/solved-problems-with-safari-4-nginx-and-connections-being-reset/</link>
		<comments>http://outsourcedclue.com/2009/04/16/solved-problems-with-safari-4-nginx-and-connections-being-reset/#comments</comments>
		<pubDate>Thu, 16 Apr 2009 16:38:22 +0000</pubDate>
		<dc:creator>sleach</dc:creator>
				<category><![CDATA[Troubleshooting]]></category>
		<category><![CDATA[apache]]></category>
		<category><![CDATA[nginx]]></category>
		<category><![CDATA[safari]]></category>

		<guid isPermaLink="false">http://outsourcedclue.com/?p=28</guid>
		<description><![CDATA[We had some issues with Safari 4 (only) and our Nginx load balancer setup. Turns out, it doesn&#8217;t like the keep alive settings to be anything but 0.  The default for nginx was 65, which for the Safari 4 users, the site would consistently not provide the full content back to the client (we use [...]]]></description>
		<wfw:commentRss>http://outsourcedclue.com/2009/04/16/solved-problems-with-safari-4-nginx-and-connections-being-reset/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Supporting &#8220;dig +trace&#8221; using an Unbound recursive/caching DNS server</title>
		<link>http://outsourcedclue.com/2009/04/13/supporting-dig-trace-using-an-unbound-recursive-dns-server/</link>
		<comments>http://outsourcedclue.com/2009/04/13/supporting-dig-trace-using-an-unbound-recursive-dns-server/#comments</comments>
		<pubDate>Mon, 13 Apr 2009 16:59:50 +0000</pubDate>
		<dc:creator>sleach</dc:creator>
				<category><![CDATA[DNS]]></category>
		<category><![CDATA[Troubleshooting]]></category>
		<category><![CDATA[dig]]></category>
		<category><![CDATA[unbound]]></category>

		<guid isPermaLink="false">http://outsourcedclue.com/?p=19</guid>
		<description><![CDATA[dig +trace example.com is an extremely useful debugging tool with DNS.  It will walk the delegation path, showing the answer each authoritative DNS server in the path handed out, helping you track down some obscure DNS errors.  For example, here is a dig +trace for &#8220;outsourcedclue.com&#8221;.   ; &#60;&#60;&#62;&#62; DiG 9.6.0-P1 &#60;&#60;&#62;&#62; +trace outsourcedclue.com ;; [...]]]></description>
		<wfw:commentRss>http://outsourcedclue.com/2009/04/13/supporting-dig-trace-using-an-unbound-recursive-dns-server/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Broken Caching DNS Server Causes Headaches</title>
		<link>http://outsourcedclue.com/2008/06/05/broken-caching-dns-server-causes-headaches/</link>
		<comments>http://outsourcedclue.com/2008/06/05/broken-caching-dns-server-causes-headaches/#comments</comments>
		<pubDate>Thu, 05 Jun 2008 12:55:03 +0000</pubDate>
		<dc:creator>sleach</dc:creator>
				<category><![CDATA[DNS]]></category>
		<category><![CDATA[Troubleshooting]]></category>
		<category><![CDATA[http]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[theplanet]]></category>

		<guid isPermaLink="false">http://outsourcedclue.com/app/?p=3</guid>
		<description><![CDATA[By now you have read the many reports of The Planet&#8217;s data center fire. Long story short, there was an explosion on the first floor of their Houston facility (old ev1servers data center) that affected network connectivity, servers and a ton of other items. Some buddies of mine, Pelago, have their gear in this facility. [...]]]></description>
		<wfw:commentRss>http://outsourcedclue.com/2008/06/05/broken-caching-dns-server-causes-headaches/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

