<?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 for BurstOpen</title>
	<atom:link href="http://burstopen.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://burstopen.com</link>
	<description>Open source web development</description>
	<lastBuildDate>Sun, 24 Jul 2011 04:41:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>Comment on Test before DNS propagates by Chris</title>
		<link>http://burstopen.com/how-to/change-hosts/testing-before-dns-propagation/comment-page-1/#comment-17817</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Sun, 24 Jul 2011 04:41:21 +0000</pubDate>
		<guid isPermaLink="false">http://burstopen.com/how-to/change-hosts/testing-before-dns-propagation/#comment-17817</guid>
		<description>You can&#039;t. DNS (and the hosts file) is only for translating a host name to an IP address. So www.example.com gets translated to 123.123.123.123. But the mod_userdir format (123.123.123.123/~sitename) is itself just another workaround to do the same job - viewing a website before the DNS has propagated - you don&#039;t ever need to use both.

So if you have a website that&#039;s available as http://123.123.123.123/~sitename it should also be available as http://sitename.com, with sitename.com being whatever domain you set up at your host, provided that DNS (or the hosts file) connects 123.123.123.123 to sitename.com. I don&#039;t see why this would require you to change anything in the databases unless you&#039;re deliberately setting up the website on 123.123.123.123/~sitename, which would be a very bad idea - requiring you to change these details anyway before the site goes live.</description>
		<content:encoded><![CDATA[<p>You can&#8217;t. DNS (and the hosts file) is only for translating a host name to an IP address. So www.example.com gets translated to 123.123.123.123. But the mod_userdir format (123.123.123.123/~sitename) is itself just another workaround to do the same job &#8211; viewing a website before the DNS has propagated &#8211; you don&#8217;t ever need to use both.</p>
<p>So if you have a website that&#8217;s available as http://123.123.123.123/~sitename it should also be available as http://sitename.com, with sitename.com being whatever domain you set up at your host, provided that DNS (or the hosts file) connects 123.123.123.123 to sitename.com. I don&#8217;t see why this would require you to change anything in the databases unless you&#8217;re deliberately setting up the website on 123.123.123.123/~sitename, which would be a very bad idea &#8211; requiring you to change these details anyway before the site goes live.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Test before DNS propagates by Wabber</title>
		<link>http://burstopen.com/how-to/change-hosts/testing-before-dns-propagation/comment-page-1/#comment-17804</link>
		<dc:creator>Wabber</dc:creator>
		<pubDate>Sat, 23 Jul 2011 21:57:26 +0000</pubDate>
		<guid isPermaLink="false">http://burstopen.com/how-to/change-hosts/testing-before-dns-propagation/#comment-17804</guid>
		<description>I&#039;m trying to redirect the site locally using the windows hosts file but not sure about the format - the traditional format works file:
123.123.123.123     www.example.com

but in this case we&#039;d like it to redirect to 123.123.123.123/~sitename

When I enter the below though it doesn&#039;t work:
123.123.123.123/~sitename     www.example.com

Any suggestions as to how I might fix this using the HOSTS file - I&#039;d rather not play around with the phpadmin and databases if possible?</description>
		<content:encoded><![CDATA[<p>I&#8217;m trying to redirect the site locally using the windows hosts file but not sure about the format &#8211; the traditional format works file:<br />
123.123.123.123     www.example.com</p>
<p>but in this case we&#8217;d like it to redirect to 123.123.123.123/~sitename</p>
<p>When I enter the below though it doesn&#8217;t work:<br />
123.123.123.123/~sitename     www.example.com</p>
<p>Any suggestions as to how I might fix this using the HOSTS file &#8211; I&#8217;d rather not play around with the phpadmin and databases if possible?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

