<?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: Weekend Roundup: Hamburgers, Investing, and Windfalls</title>
	<atom:link href="http://www.getrichslowly.org/blog/2007/09/15/weekend-roundup-hamburgers-investing-and-windfalls/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.getrichslowly.org/blog/2007/09/15/weekend-roundup-hamburgers-investing-and-windfalls/</link>
	<description>Common sense advice on money saving tips, how to get out of debt, high interest savings accounts, cd rates, money market accounts, mortgage rates, money management and more.</description>
	<lastBuildDate>Wed, 19 Jun 2013 21:32:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Daniel</title>
		<link>http://www.getrichslowly.org/blog/2007/09/15/weekend-roundup-hamburgers-investing-and-windfalls/comment-page-1/#comment-98026</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Thu, 20 Sep 2007 11:04:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.getrichslowly.org/blog/2007/09/15/weekend-roundup-hamburgers-investing-and-windfalls/#comment-98026</guid>
		<description>Hi JD.

It is a fallacy that web sites might be unreachable for days just because the address changes.  When done properly, nobody ever notices any downtime.

The proper way to do it is exactly what you did:
- make backup of existing server
- copy files to new server
- configure and launch new server
- change DNS to address of new server

It may take a while (usually 12-24 hours, typically not &quot;days,&quot; unless your domain configuration is different from most) for the change to propagate everywhere, and this is only because of address caching - whenever you request a web site&#039;s address, the DNS servers don&#039;t grab that info every time - they consult their caches, and return the address in the cache if it is there.  If the address is not in the cache, web users will see the new site the instant you flip the switch.

The cache ages, and the address goes away after a time.  In fact, you control that time - it is known as the TTL (tme to live) in the SOA (start of authority) record of your domain name configuration.  Your provider probably gives you access to those settings in an advance configuration screen.

Cheers.</description>
		<content:encoded><![CDATA[<p>Hi JD.</p>
<p>It is a fallacy that web sites might be unreachable for days just because the address changes.  When done properly, nobody ever notices any downtime.</p>
<p>The proper way to do it is exactly what you did:<br />
- make backup of existing server<br />
- copy files to new server<br />
- configure and launch new server<br />
- change DNS to address of new server</p>
<p>It may take a while (usually 12-24 hours, typically not &#8220;days,&#8221; unless your domain configuration is different from most) for the change to propagate everywhere, and this is only because of address caching &#8211; whenever you request a web site&#8217;s address, the DNS servers don&#8217;t grab that info every time &#8211; they consult their caches, and return the address in the cache if it is there.  If the address is not in the cache, web users will see the new site the instant you flip the switch.</p>
<p>The cache ages, and the address goes away after a time.  In fact, you control that time &#8211; it is known as the TTL (tme to live) in the SOA (start of authority) record of your domain name configuration.  Your provider probably gives you access to those settings in an advance configuration screen.</p>
<p>Cheers.</p>
<div id="placeholer-like-98026" class="likediv"><p>loading....</p></div>]]></content:encoded>
	</item>
</channel>
</rss>
