<?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>Domain Advice &#187; GoDaddy</title>
	<atom:link href="http://www.domain-advice.com/webhosting/tag/godaddy/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.domain-advice.com</link>
	<description>Domain names, domain registars, and webhosting help.</description>
	<lastBuildDate>Sun, 06 Dec 2009 03:20:55 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>eNom Whois Trouble Due To Registry Operator</title>
		<link>http://www.domain-advice.com/webhosting/79/enom-whois-trouble-due-to-registry-operator/</link>
		<comments>http://www.domain-advice.com/webhosting/79/enom-whois-trouble-due-to-registry-operator/#comments</comments>
		<pubDate>Fri, 03 Oct 2008 03:14:18 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Domain Names]]></category>
		<category><![CDATA[Domain Name Registrars]]></category>
		<category><![CDATA[eNom]]></category>
		<category><![CDATA[GoDaddy]]></category>
		<category><![CDATA[whois]]></category>

		<guid isPermaLink="false">http://www.domain-advice.com/?p=79</guid>
		<description><![CDATA[When I called eNom, their tech support rep tried to tell me it was a problem with the registry operator and how they display their data. Not as bad as the GoDaddy rep who told me I needed to pay for an upgraded &#8220;business listing&#8221; in order to update my whois record the day before.

]]></description>
			<content:encoded><![CDATA[<p><span style="font-family: Arial,Helvetica; font-size: small;">When I called eNom, their tech support rep tried to tell me it was a problem with the registry operator and how they display their data. Not as bad as the GoDaddy rep who told me I needed to pay for an upgraded &#8220;business listing&#8221; in order to update my whois record the day before.<span><br />
</span></span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.domain-advice.com/webhosting/79/enom-whois-trouble-due-to-registry-operator/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>GoDaddy Gets RegisterFly Domains</title>
		<link>http://www.domain-advice.com/webhosting/42/godaddy-gets-registerfly-domains/</link>
		<comments>http://www.domain-advice.com/webhosting/42/godaddy-gets-registerfly-domains/#comments</comments>
		<pubDate>Wed, 30 May 2007 02:54:00 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Domain Names]]></category>
		<category><![CDATA[Bob Parsons]]></category>
		<category><![CDATA[GoDaddy]]></category>
		<category><![CDATA[ICANN]]></category>
		<category><![CDATA[RegisterFly]]></category>
		<category><![CDATA[Registrar Fraud]]></category>

		<guid isPermaLink="false">http://www.domain-advice.com/?p=42</guid>
		<description><![CDATA[The final chapter on RegisterFly will be massive ICANN changes, the second-to-last chapter will be the lawsuits, but the first of the last chapters is how the domains went from RegisterFly to GoDaddy. As the article leads, &#8220;Bob Parsons has hit a homerun.&#8221; Indeed. 
GoDaddy Scores 850,000 Domains From RegisterFly

]]></description>
			<content:encoded><![CDATA[<p><span style="font-family: Arial,Helvetica; font-size: small;">The final chapter on RegisterFly will be massive ICANN changes, the second-to-last chapter will be the lawsuits, but the first of the last chapters is how the domains went from RegisterFly to GoDaddy. As the article leads, &#8220;Bob Parsons has hit a homerun.&#8221; Indeed.<span> </span><br />
<strong><a href="http://blog.wired.com/business/2007/05/godaddy_scores_.html">GoDaddy Scores 850,000 Domains From RegisterFly</a></strong><span><br />
</span></span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.domain-advice.com/webhosting/42/godaddy-gets-registerfly-domains/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>GoDaddy Kills Website</title>
		<link>http://www.domain-advice.com/webhosting/17/godaddy-kills-website/</link>
		<comments>http://www.domain-advice.com/webhosting/17/godaddy-kills-website/#comments</comments>
		<pubDate>Sat, 27 Jan 2007 02:15:00 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Domain Names]]></category>
		<category><![CDATA[GoDaddy]]></category>
		<category><![CDATA[MySpace]]></category>
		<category><![CDATA[TOS]]></category>
		<category><![CDATA[User Generated Content]]></category>

		<guid isPermaLink="false">http://www.domain-advice.com/?p=17</guid>
		<description><![CDATA[GoDaddy is becoming more and more proactive about violations of its TOS. In this case they brought down a domain because MySpace complained that it had listed user passwords. Word to the wise: don&#8217;t use GoDaddy if you have any user-generated content.
GoDaddy makes site go away
]]></description>
			<content:encoded><![CDATA[<p><span style="font-family: Arial,Helvetica;"><span style="font-family: Arial,Helvetica;"><span><span style="font-family: Arial,Helvetica;"><span style="font-family: Arial,Helvetica;">GoDaddy is becoming more and more proactive about violations of its TOS. In this case they brought down a domain because MySpace complained that it had listed user passwords. Word to the wise: don&#8217;t use GoDaddy if you have any user-generated content.<br />
<strong><a href="http://news.com.com/GoDaddy+pulls+security+site+after+MySpace+complaints/2100-1025_3-6153607.html?tag=nefd.lede">GoDaddy makes site go away</a></strong></span></span></span></span></span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.domain-advice.com/webhosting/17/godaddy-kills-website/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
