<?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: Tip about domain parking</title>
	<atom:link href="http://www.memwg.com/tip-about-domain-parking/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.memwg.com/tip-about-domain-parking/</link>
	<description>Google AdSense Tips and Advice</description>
	<lastBuildDate>Tue, 13 Apr 2010 23:47:59 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Colin</title>
		<link>http://www.memwg.com/tip-about-domain-parking/comment-page-1/#comment-2896</link>
		<dc:creator>Colin</dc:creator>
		<pubDate>Mon, 28 Jan 2008 16:31:16 +0000</pubDate>
		<guid isPermaLink="false">http://memwg.com/general/tip-about-domain-parking/#comment-2896</guid>
		<description>Oddly enough I just transferred a domain that I sold when I read this.  I manage my DNS so I started prep by reducing the cache time down to an hour for my name servers.  Everything checked out ok.  Then as we got close I reduced down to 5 minutes and found out - my ISP won&#039;t honor that!  So they defaulted to 48 hours!  Now anyone on my ISP has to wait 48 hours.

I guess the lesson learned for me is don&#039;t go to less than an hour on the nameservers :)  And the hosts file idea works great to bypass your ISP.  If you run your own server or cache at home (like for a multi-site development environment) you can also declare anything as a private domain and point it in the right direction as well.  This also works great (but overly complicated) to point one or two obnoxious pop-up domains into the ether for your whole network.</description>
		<content:encoded><![CDATA[<p>Oddly enough I just transferred a domain that I sold when I read this.  I manage my DNS so I started prep by reducing the cache time down to an hour for my name servers.  Everything checked out ok.  Then as we got close I reduced down to 5 minutes and found out &#8211; my ISP won&#8217;t honor that!  So they defaulted to 48 hours!  Now anyone on my ISP has to wait 48 hours.</p>
<p>I guess the lesson learned for me is don&#8217;t go to less than an hour on the nameservers <img src='http://www.memwg.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />   And the hosts file idea works great to bypass your ISP.  If you run your own server or cache at home (like for a multi-site development environment) you can also declare anything as a private domain and point it in the right direction as well.  This also works great (but overly complicated) to point one or two obnoxious pop-up domains into the ether for your whole network.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk (enhanced) (user agent is rejected)
Database Caching 9/18 queries in 0.017 seconds using disk

Served from: www.memwg.com @ 2010-07-29 13:18:49 -->