<?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>apache Archives  | Eric Thern :: thern dot org ::</title>
	<atom:link href="http://thern.org/category/system-administration/apache-system-administration/feed/" rel="self" type="application/rss+xml" />
	<link>http://thern.org</link>
	<description>Migrating servers to new datacenters or IP addresses is never entirely problem free, usually due to many DNS servers on the internet not obeying TTL&#8217;s or caching old records for way too long.
These old cached DNS records (usually at different ISP&#8217;s, major mailservers like google, hotmail, yahoo, etc.) cause problems where they&#8217;ll route mail to your old server&#8217;s IP even if you update your DNS.  This also results in clients connecting to your old web IP address and not hitting your new server.
When migrating static html sites, having two servers online during a migration isn&#8217;t a real issue, but when you&#8217;ve got database driven websites (forums, blogs, etc.) this will result in updates going to two different sites, causing all sorts of hassles.  The way around this is to set up your old site as a proxy only, and proxy the results to the new IP address.
Here&#8217;s some configs to allow for proxying Web traffic via Apache, DNS t</description>
	<lastBuildDate>Thu, 04 Aug 2011 18:28:29 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>apache Archives  | Eric Thern :: thern dot org ::</title>
		<link>http://thern.org/system-administration/minimizing-downtime-associated-with-webdnsmail-ip-address-migrations/</link>
		<comments>http://thern.org/system-administration/minimizing-downtime-associated-with-webdnsmail-ip-address-migrations/#comments</comments>
		<pubDate>Sat, 03 Apr 2010 00:45:34 +0000</pubDate>
		<dc:creator>Eric Thern</dc:creator>
				<category><![CDATA[apache]]></category>
		<category><![CDATA[linux & freebsd]]></category>
		<category><![CDATA[sendmail]]></category>
		<category><![CDATA[system administration]]></category>
		<category><![CDATA[centos]]></category>
		<category><![CDATA[dns proxy]]></category>
		<category><![CDATA[ip address]]></category>
		<category><![CDATA[ip migration]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[mailertable]]></category>
		<category><![CDATA[mod_proxy]]></category>
		<category><![CDATA[named]]></category>
		<category><![CDATA[nameservers]]></category>
		<category><![CDATA[relay-domains]]></category>
		<category><![CDATA[ttl]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://thern.org/?p=201</guid>
		<description><![CDATA[<p>Migrating servers to new datacenters or IP addresses is never entirely problem free, usually due to many DNS servers on the internet not obeying TTL&#8217;s or caching old records for way too long.</p> <p>These old cached DNS records (usually at different ISP&#8217;s, major mailservers like google, hotmail, yahoo, etc.) cause problems where they&#8217;ll route mail [...]]]></description>
		<wfw:commentRss>http://thern.org/system-administration/minimizing-downtime-associated-with-webdnsmail-ip-address-migrations/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>apache Archives  | Eric Thern :: thern dot org ::</title>
		<link>http://thern.org/system-administration/apache-system-administration/moving-wordpress-from-a-subdirectory-and-generation-of-301-redirects-from-a-google-sitemap/</link>
		<comments>http://thern.org/system-administration/apache-system-administration/moving-wordpress-from-a-subdirectory-and-generation-of-301-redirects-from-a-google-sitemap/#comments</comments>
		<pubDate>Thu, 25 Feb 2010 02:27:00 +0000</pubDate>
		<dc:creator>Eric Thern</dc:creator>
				<category><![CDATA[apache]]></category>
		<category><![CDATA[301 redirect]]></category>
		<category><![CDATA[awk]]></category>
		<category><![CDATA[htaccess]]></category>
		<category><![CDATA[moving directory]]></category>
		<category><![CDATA[redirect]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://thern.org/?p=180</guid>
		<description><![CDATA[<p>So I mistakenly have installed wordpress in a subdirectory on my site &#8211; this worked well for testing, but I didn&#8217;t buy this domain to have my entire site sitting within a subdirectory!</p> <p>WordPress has a good guide on this subject, which has step by step instructions on migrating your installation from one directory to [...]]]></description>
		<wfw:commentRss>http://thern.org/system-administration/apache-system-administration/moving-wordpress-from-a-subdirectory-and-generation-of-301-redirects-from-a-google-sitemap/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>apache Archives  | Eric Thern :: thern dot org ::</title>
		<link>http://thern.org/system-administration/freebsd/freebsd-plesk-8-installing-php5-as-cgi-alongside-php4/</link>
		<comments>http://thern.org/system-administration/freebsd/freebsd-plesk-8-installing-php5-as-cgi-alongside-php4/#comments</comments>
		<pubDate>Sun, 25 Nov 2007 22:22:21 +0000</pubDate>
		<dc:creator>Eric Thern</dc:creator>
				<category><![CDATA[apache]]></category>
		<category><![CDATA[freebsd]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[plesk]]></category>
		<category><![CDATA[freebsd 6.x]]></category>
		<category><![CDATA[php4]]></category>
		<category><![CDATA[php5]]></category>
		<category><![CDATA[plesk 8.0.x]]></category>

		<guid isPermaLink="false">http://thern.org/eric/?p=60</guid>
		<description><![CDATA[<p>If you have ever needed php5 to run along side php4, you can always compile php5 as a CGI, and let php4 remain as an apache module.</p> <p>Here we&#8217;ve compiled php5 from FreeBSD&#8217;s ports, and have installed it as a CGI so that specific vhosts will run on this new php5. The installation was done [...]]]></description>
		<wfw:commentRss>http://thern.org/system-administration/freebsd/freebsd-plesk-8-installing-php5-as-cgi-alongside-php4/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>apache Archives  | Eric Thern :: thern dot org ::</title>
		<link>http://thern.org/system-administration/apache-system-administration/dealing-with-apache-referrer-spam/</link>
		<comments>http://thern.org/system-administration/apache-system-administration/dealing-with-apache-referrer-spam/#comments</comments>
		<pubDate>Fri, 28 Sep 2007 22:14:25 +0000</pubDate>
		<dc:creator>Eric Thern</dc:creator>
				<category><![CDATA[apache]]></category>
		<category><![CDATA[apache ddos spam]]></category>
		<category><![CDATA[apache referrer ddos]]></category>
		<category><![CDATA[apache referrer spam]]></category>
		<category><![CDATA[awk]]></category>
		<category><![CDATA[bash]]></category>
		<category><![CDATA[grep]]></category>
		<category><![CDATA[httpd.conf]]></category>
		<category><![CDATA[mod_rewrite]]></category>
		<category><![CDATA[mod_rewrite blocking of spam]]></category>
		<category><![CDATA[sort]]></category>
		<category><![CDATA[spam]]></category>

		<guid isPermaLink="false">http://thern.org/eric/2009/09/21/48/</guid>
		<description><![CDATA[<p>I&#8217;ve had a number of sites get hammered by referrer spam lately, and had to look into methods of stopping, or at least slowing the attacks.</p> <p></p> <p>Referrer spam is when a group of random (probably trojan or hacked computers) or single computers hit random pages on your site with faked referrer values, typically all [...]]]></description>
		<wfw:commentRss>http://thern.org/system-administration/apache-system-administration/dealing-with-apache-referrer-spam/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

