<?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: Google Offers Domain Name Registration</title>
	<atom:link href="http://www.reprisemedia.com/searchviews/2006/12/google-offers-domain-name-registration/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.reprisemedia.com/searchviews/2006/12/google-offers-domain-name-registration/</link>
	<description>Welcome to Searchviews, where Reprise Media and our employees can express their views on what&#039;s going on in the world of search and social media.</description>
	<lastBuildDate>Fri, 05 Dec 2008 19:18:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: Dee</title>
		<link>http://www.reprisemedia.com/searchviews/2006/12/google-offers-domain-name-registration/comment-page-1/#comment-2601</link>
		<dc:creator>Dee</dc:creator>
		<pubDate>Sun, 04 May 2008 18:00:34 +0000</pubDate>
		<guid isPermaLink="false">http://blogbeta.reprisemedia.com/?p=2056#comment-2601</guid>
		<description>So, is there a way to do this on your own eliminating the headache of it all?</description>
		<content:encoded><![CDATA[<p>So, is there a way to do this on your own eliminating the headache of it all?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven</title>
		<link>http://www.reprisemedia.com/searchviews/2006/12/google-offers-domain-name-registration/comment-page-1/#comment-2587</link>
		<dc:creator>Steven</dc:creator>
		<pubDate>Mon, 28 Apr 2008 00:51:51 +0000</pubDate>
		<guid isPermaLink="false">http://blogbeta.reprisemedia.com/?p=2056#comment-2587</guid>
		<description>Actually, AJ is exactly right.

In fact, Google is an ENOM reseller, and we all know what that means - customers are never quite in full control of their domain names when they buy them through Enom resellers. Don&#039;t believe me? Register a domain name through any Enom reseller, and then try to transfer the domain to a different registrar someday. 

Enom won&#039;t help you (unless you waste a bunch of time filing complaints and jump through a week&#039;s worth of hoops / red tape) because they have a contract with the reseller, and 9 times out of 10 the reseller will not turn over full control to the registrant - forcing the registrant to ask the reseller to allow the transfer subsmission / obtain auth codes / etc... because they don&#039;t want to lose the registrant to another registrar or hosting company. 

I&#039;ve been down this road a million times, since setting up domains and hosting for people is what I do for a living, and at least 90% of the Enom resellers I&#039;ve encountered have this shady practice of holding domains hostage / ignoring customer requests for  nameserver updates and domain transfers.

One positive thing I can say for Google&#039;s Enom reseller feature that I can&#039;t say for the rest, is that at least Google currently gives the domain owner access to SOME of the necessary domain controls at https://access.enom.com/domainmain.asp - at least in there the owner can update the nameserver DNS to move a site to a new host. However, you won&#039;t find any way to transfer the domain to a different registrar in there, nor your auth codes for transfers. It is a somewhat crippled domain management panel, but at least it&#039;s better than none at all (unlike what you get from most Enom resellers, which is nothing but a run-around and no access).

So the bottom line is:

Pros - You can register a domain through Google

Cons - It&#039;s still under an Enom reseller account, and be prepared for a lot of frustration should you decide to transfer your domain or have &quot;full&quot; control.</description>
		<content:encoded><![CDATA[<p>Actually, AJ is exactly right.</p>
<p>In fact, Google is an ENOM reseller, and we all know what that means &#8211; customers are never quite in full control of their domain names when they buy them through Enom resellers. Don&#8217;t believe me? Register a domain name through any Enom reseller, and then try to transfer the domain to a different registrar someday. </p>
<p>Enom won&#8217;t help you (unless you waste a bunch of time filing complaints and jump through a week&#8217;s worth of hoops / red tape) because they have a contract with the reseller, and 9 times out of 10 the reseller will not turn over full control to the registrant &#8211; forcing the registrant to ask the reseller to allow the transfer subsmission / obtain auth codes / etc&#8230; because they don&#8217;t want to lose the registrant to another registrar or hosting company. </p>
<p>I&#8217;ve been down this road a million times, since setting up domains and hosting for people is what I do for a living, and at least 90% of the Enom resellers I&#8217;ve encountered have this shady practice of holding domains hostage / ignoring customer requests for  nameserver updates and domain transfers.</p>
<p>One positive thing I can say for Google&#8217;s Enom reseller feature that I can&#8217;t say for the rest, is that at least Google currently gives the domain owner access to SOME of the necessary domain controls at <a href="https://access.enom.com/domainmain.asp" rel="nofollow">https://access.enom.com/domainmain.asp</a> &#8211; at least in there the owner can update the nameserver DNS to move a site to a new host. However, you won&#8217;t find any way to transfer the domain to a different registrar in there, nor your auth codes for transfers. It is a somewhat crippled domain management panel, but at least it&#8217;s better than none at all (unlike what you get from most Enom resellers, which is nothing but a run-around and no access).</p>
<p>So the bottom line is:</p>
<p>Pros &#8211; You can register a domain through Google</p>
<p>Cons &#8211; It&#8217;s still under an Enom reseller account, and be prepared for a lot of frustration should you decide to transfer your domain or have &#8220;full&#8221; control.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Griffin</title>
		<link>http://www.reprisemedia.com/searchviews/2006/12/google-offers-domain-name-registration/comment-page-1/#comment-1521</link>
		<dc:creator>Griffin</dc:creator>
		<pubDate>Mon, 24 Sep 2007 00:21:06 +0000</pubDate>
		<guid isPermaLink="false">http://blogbeta.reprisemedia.com/?p=2056#comment-1521</guid>
		<description>Sour grapes, Ajay? ;)</description>
		<content:encoded><![CDATA[<p>Sour grapes, Ajay? <img src='http://www.reprisemedia.com/searchviews/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ajay</title>
		<link>http://www.reprisemedia.com/searchviews/2006/12/google-offers-domain-name-registration/comment-page-1/#comment-1224</link>
		<dc:creator>Ajay</dc:creator>
		<pubDate>Sat, 16 Dec 2006 08:06:54 +0000</pubDate>
		<guid isPermaLink="false">http://blogbeta.reprisemedia.com/?p=2056#comment-1224</guid>
		<description>IMO, the only persons that Google will succeed in targeting are those who are unable to do domain configuration themselves as well as those who want the privacy registration.

For other users it would work out cheaper to just register a domain name and do the configuration yourself, like I have done for two of my domains.

</description>
		<content:encoded><![CDATA[<p>IMO, the only persons that Google will succeed in targeting are those who are unable to do domain configuration themselves as well as those who want the privacy registration.</p>
<p>For other users it would work out cheaper to just register a domain name and do the configuration yourself, like I have done for two of my domains.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

