<?xml version="1.0" encoding="utf-8" ?>

<rss version="2.0" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   >
<channel>
    <title>Exile From the Herd - via easyDNS blog</title>
    <link>http://www.privateworld.com/</link>
    <description>Better Living through Private World Domination</description>
    <dc:language>en</dc:language>
    <generator>Serendipity 1.0-beta3 - http://www.s9y.org/</generator>
    <pubDate>Fri, 05 Mar 2010 02:44:23 GMT</pubDate>

    <image>
        <url>http://www.privateworld.com/templates/default/img/s9y_banner_small.png</url>
        <title>RSS: Exile From the Herd - via easyDNS blog - Better Living through Private World Domination</title>
        <link>http://www.privateworld.com/</link>
        <width>100</width>
        <height>21</height>
    </image>

<item>
    <title>.CO Domain Registrations are Coming. Will You Participate?</title>
    <link>http://www.privateworld.com/archives/237-.CO-Domain-Registrations-are-Coming.-Will-You-Participate.html</link>
            <category>via easyDNS blog</category>
    
    <comments>http://www.privateworld.com/archives/237-.CO-Domain-Registrations-are-Coming.-Will-You-Participate.html#comments</comments>
    <wfw:comment>http://www.privateworld.com/wfwcomment.php?cid=237</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.privateworld.com/rss.php?version=2.0&amp;type=comments&amp;cid=237</wfw:commentRss>
    

    <author>nospam@example.com (easyDNS: Domain Industry Watch)</author>
    <content:encoded>
    &lt;br /&gt;
    A bunch of years ago I had an idea for an espionage/action/thriller story where a bunch of mercenaries planned a coup d&#039;etat against the regimes of either Columbia or Cameroon for the sole reason of gaining control over the country&#039;s top-level domain registry and making billions off of typo-squatting .COM.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
Truth did kind of mimic fiction (minus the coup d&#039;etat part) when &lt;a href=&quot;http://money.cnn.com/magazines/business2/business2_archive/2007/06/01/100050989/index.htm&quot; target=&quot;new&quot;&gt;Kevin Ham cut a deal with Cameroon to wildcard .CM root&lt;/a&gt;. Well now Columbia has decided to overhaul it&#039;s .CO root level domain and open it up to second level registations for non-locals.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
.CO is being marketed ostensibly as &#039;Associated globally with the words &quot;COmpany,&quot;&quot;COrporation&quot; and &quot;COmmerce&quot;&#039;, but let&#039;s face it, the activity in this TLD is going to be driven primarily by the fact that it&#039;s a typosquatter&#039;s wet dream for .COM and a goddamn headache for everybody else with a net presence built mainly under .COM.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
As we&#039;ve observed before (&lt;a href=&quot;http://blog.easydns.org/archives/219-.ME-Top-Level-Domain-launch-indicative-of-new-TLD-rollouts.html&quot; target=&quot;new&quot;&gt;here&lt;/a&gt; and then &lt;a href=&quot;http://blog.easydns.org/archives/264-Do-you-really-need-to-register-your-name-under-.tel.html&quot; target=&quot;new&quot;&gt;here&lt;/a&gt;), most registrars like to whip their customer base into a frenzy to &quot;grab your name&quot; under every TLD that tries to tart itself up as some pseudo-generic and trots itself out as the latest &quot;must-have&quot; domain. Most of them aren&#039;t &quot;must-haves&quot; and a lot of them are quite frankly, a waste of time and money.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
So it is with a heavy heart I have to come out and say this. If you&#039;re operating a serious net presence on .COM, you probably should go out and get the  .CO version of your name, as much of a royal pain in the ass as that is/will be. Not to mention expensive. The base cost on a non-Columbian Sunrise claim will be somewhere north of $250 (non-refundable) and for landrush there will be a small non-refundable &quot;application fee&quot; but the first year registration will be over $200. Then after landrush, the cost will settle down to a more digestible level, only about 3 times the wholesale base cost of an actual .COM.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
Nice work if you can get it.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
We don&#039;t want to make a bad situation worse, but we won&#039;t work for free either, so we&#039;ll try to keep our markup reasonable.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
What I am interested in is what our members think of this. If you have a few moments, please take the following survey on whether you will participate in .CO. For each response we&#039;ll donate $1 to the charity of your choice. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
Feel free to comment as well.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href=&quot;http://blog.easydns.org/archives/314-.CO-Domain-Registrations-are-Coming.-Will-You-Participate.html#extended&quot;&gt;Continue reading &quot;.CO Domain Registrations are Coming. Will You Participate?&quot;&lt;/a&gt; 
    </content:encoded>

    <pubDate>Thu, 04 Mar 2010 21:44:23 -0500</pubDate>
    <guid isPermaLink="false">http://www.privateworld.com/archives/237-guid.html</guid>
    
</item>
<item>
    <title>easyURL.net now CLOSED to general public</title>
    <link>http://www.privateworld.com/archives/221-easyURL.net-now-CLOSED-to-general-public.html</link>
            <category>via easyDNS blog</category>
    
    <comments>http://www.privateworld.com/archives/221-easyURL.net-now-CLOSED-to-general-public.html#comments</comments>
    <wfw:comment>http://www.privateworld.com/wfwcomment.php?cid=221</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.privateworld.com/rss.php?version=2.0&amp;type=comments&amp;cid=221</wfw:commentRss>
    

    <author>nospam@example.com (easyDNS: of Interest)</author>
    <content:encoded>
    &lt;br /&gt;
    Our URL shortening service &lt;a href=&quot;http://www.easyURL.net&quot;&gt;easyURL.net&lt;/a&gt; is now &lt;b&gt;CLOSED&lt;/b&gt; to the general public.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
Only easyDNS members in good standing with at least one active domain in their account may use this service. To enable your access log into your easyDNS account and under your &lt;b&gt;utilities&lt;/b&gt; module click on &lt;b&gt;enable easyURL.net&lt;/b&gt; and then you&#039;re done. Happy shortening.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
Everybody else can make other arrangements. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
Thank you for your time. &lt;br /&gt;
     
    </content:encoded>

    <pubDate>Tue, 01 Sep 2009 14:19:39 -0400</pubDate>
    <guid isPermaLink="false">http://www.privateworld.com/archives/221-guid.html</guid>
    
</item>
<item>
    <title>easyURL.net adds useless &quot;easyFrame&quot; to redirects.</title>
    <link>http://www.privateworld.com/archives/219-easyURL.net-adds-useless-easyFrame-to-redirects..html</link>
            <category>via easyDNS blog</category>
    
    <comments>http://www.privateworld.com/archives/219-easyURL.net-adds-useless-easyFrame-to-redirects..html#comments</comments>
    <wfw:comment>http://www.privateworld.com/wfwcomment.php?cid=219</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.privateworld.com/rss.php?version=2.0&amp;type=comments&amp;cid=219</wfw:commentRss>
    

    <author>nospam@example.com (easyDNS: of Interest)</author>
    <content:encoded>
    &lt;br /&gt;
    Feeling left out of the web 2.0 &quot;URL Shortener&quot; hysteria, we&#039;ve added a mostly useless &quot;easyFrame&quot;&amp;trade; to the easyURL.net redirect service. The culmination of nearly two night&#039;s worth of programming in front of the TV, and nearing 100 lines of PHP code, the easyFrame&amp;trade; enables people to further perpetuate it&#039;s marginal functionality via other social networking sites with a single click. Users may also &quot;vote&quot; on whether they actually like or dislike the subject URL being shortened.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;&lt;br /&gt;&lt;br /&gt;
Perhaps the single actual useful function of the easyFrame&amp;trade; is that you can also report spam URLs directly to us, with one click, which we will then nuke with extreme prejudice.&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
We are also happy to report that our new easyFrame&amp;trade; has enticed a VC bidding war and easyURL has closed a $30 Million dollar A series funding round with a pre-money valuation more than 100X that of easyDNS itself. We are now planning on spinning off easyURL.net in an October IPO.&lt;br /&gt;&lt;br /&gt;&lt;a href=&quot;http://easyurl.net&quot;&gt;Try it today! Tell your friends!&lt;/a&gt;&lt;a href=&quot;http://twitter.com/home?status=http://easyurl.net/easyframe&quot;&gt;Tweet it!&lt;/a&gt;&lt;br /&gt; 
    </content:encoded>

    <pubDate>Tue, 18 Aug 2009 23:43:37 -0400</pubDate>
    <guid isPermaLink="false">http://www.privateworld.com/archives/219-guid.html</guid>
    
</item>
<item>
    <title>Whois Privacy brings a lawsuit down on Registrar</title>
    <link>http://www.privateworld.com/archives/220-Whois-Privacy-brings-a-lawsuit-down-on-Registrar.html</link>
            <category>via easyDNS blog</category>
    
    <comments>http://www.privateworld.com/archives/220-Whois-Privacy-brings-a-lawsuit-down-on-Registrar.html#comments</comments>
    <wfw:comment>http://www.privateworld.com/wfwcomment.php?cid=220</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.privateworld.com/rss.php?version=2.0&amp;type=comments&amp;cid=220</wfw:commentRss>
    

    <author>nospam@example.com (easyDNS: Domain Industry Watch)</author>
    <content:encoded>
    &lt;br /&gt;
    Following on our explanation of why &lt;a href=&quot;http://blog.easydns.org/archives/247-Why-we-do-not-offer-Whois-masking-at-easyDNS.html&quot;&gt;we do not offer whois masking&lt;/a&gt; here at easyDNS, we note tonight that Registrar &lt;a href=&quot;http://www.domainnamenews.com/featured/namecheap-sued-domain-whois-privacy-service/5198&quot;&gt;Namecheap has been sued&lt;/a&gt;&quot;over cybersquatting claims for a domain name registered under the NameCheap whois privacy services&quot;.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
As we outlined in our original article: Whoever is listed as the Registrant in the domain&#039;s whois record, effectively owns the domain. If you own the domain, you get all the responsibilities for it. That&#039;s why most Registrars simply drop the whois mask at the slightest legal speedbump. Namecheap didn&#039;t, and so now it cuts the other way &lt;i&gt;they&lt;/i&gt; get the sharp end of the legal stick being poked at the domain.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
Technology lawyer Eric Goldman in &lt;a href=&quot;http://blog.ericgoldman.org/archives/2009/05/contributory_cy.htm&quot;&gt;his analysis of the matter&lt;/a&gt; under the subheading &lt;b&gt;Why This is a Troubling Ruling&lt;/b&gt; noted:&lt;br /&gt;&lt;br /&gt;&lt;blockquote&gt;Read literally, every proxy service is exposed to potential contributory ACPA liability for every domain name it services. I cant imagine proxy service providers will be excited about that liability exposure, and some may choose to exit the business.&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
Some certainly should. Any of the proxy providers who basically viewed whois masking as an easy business which basically pulls in money for doing nothing (which is more or less how I view it, I&#039;m sorry, but that&#039;s only my opinion) - should take this as their signal that the party&#039;s over and exit the business.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
As I&#039;ve noted before, in it&#039;s current implmentation: whois privacy doesn&#039;t actually protect the underlying registrant&#039;s privacy (because most proxy providers will drop the mask at the first sign of trouble) and if they don&#039;t, the proxy providers are exposing themselves to inordinate risk. Coupled with the fact that the whois mask puts the underlying registrant&#039;s rights to the name in question and the whole thing is just one big mess waiting to blow up.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt; 
    </content:encoded>

    <pubDate>Sat, 30 May 2009 09:30:00 -0400</pubDate>
    <guid isPermaLink="false">http://www.privateworld.com/archives/220-guid.html</guid>
    
</item>
<item>
    <title>Whois Privacy brings a lawsuit down on Registrar</title>
    <link>http://www.privateworld.com/archives/215-Whois-Privacy-brings-a-lawsuit-down-on-Registrar.html</link>
            <category>via easyDNS blog</category>
    
    <comments>http://www.privateworld.com/archives/215-Whois-Privacy-brings-a-lawsuit-down-on-Registrar.html#comments</comments>
    <wfw:comment>http://www.privateworld.com/wfwcomment.php?cid=215</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.privateworld.com/rss.php?version=2.0&amp;type=comments&amp;cid=215</wfw:commentRss>
    

    <author>nospam@example.com (easyDNS: Domain Industry Watch)</author>
    <content:encoded>
    &lt;br /&gt;
    Following on our explanation of why &lt;a href=&quot;http://blog.easydns.org/archives/247-Why-we-do-not-offer-Whois-masking-at-easyDNS.html&quot;&gt;we do not offer whois masking&lt;/a&gt; here at easyDNS, we note tonight that Registrar &lt;a href=&quot;http://www.domainnamenews.com/featured/namecheap-sued-domain-whois-privacy-service/5198&quot;&gt;Namecheap has been sued&lt;/a&gt;&quot;over cybersquatting claims for a domain name registered under the NameCheap whois privacy services&quot;.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
As we outlined in our original article: Whoever is listed as the Registrant in the domain&#039;s whois record, effectively owns the domain. If you own the domain, you get all the responsibilities for it. That&#039;s why most Registrars simply drop the whois mask at the slightest legal speedbump. Namecheap didn&#039;t, and so now it cuts the other way &lt;i&gt;they&lt;/i&gt; get the sharp end of the legal stick being poked at the domain.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
Technology lawyer Eric Goldman in &lt;a href=&quot;http://blog.ericgoldman.org/archives/2009/05/contributory_cy.htm&quot;&gt;his analysis of the matter&lt;/a&gt; under the subheading &lt;b&gt;Why This is a Troubling Ruling&lt;/b&gt; noted:&lt;br /&gt;&lt;br /&gt;&lt;blockquote&gt;Read literally, every proxy service is exposed to potential contributory ACPA liability for every domain name it services. I cant imagine proxy service providers will be excited about that liability exposure, and some may choose to exit the business.&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
Some certainly should. Any of the proxy providers who basically viewed whois masking as an easy business which basically pulls in money for doing nothing (which is more or less how I view it, I&#039;m sorry, but that&#039;s only my opinion) - should take this as their signal that the party&#039;s over and exit the business.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
As I&#039;ve noted before, in it&#039;s current implmentation: whois privacy doesn&#039;t actually protect the underlying registrant&#039;s privacy (because most proxy providers will drop the mask at the first sign of trouble) and if they don&#039;t, the proxy providers are exposing themselves to inordinate risk. Coupled with the fact that the whois mask puts the underlying registrant&#039;s rights to the name in question and the whole thing is just one big mess waiting to blow up.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt; 
    </content:encoded>

    <pubDate>Fri, 29 May 2009 22:26:42 -0400</pubDate>
    <guid isPermaLink="false">http://www.privateworld.com/archives/215-guid.html</guid>
    
</item>
<item>
    <title>Do you really need to register your name under .tel?</title>
    <link>http://www.privateworld.com/archives/209-Do-you-really-need-to-register-your-name-under-.tel.html</link>
            <category>via easyDNS blog</category>
    
    <comments>http://www.privateworld.com/archives/209-Do-you-really-need-to-register-your-name-under-.tel.html#comments</comments>
    <wfw:comment>http://www.privateworld.com/wfwcomment.php?cid=209</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.privateworld.com/rss.php?version=2.0&amp;type=comments&amp;cid=209</wfw:commentRss>
    

    <author>nospam@example.com (easyDNS: of Interest)</author>
    <content:encoded>
    &lt;br /&gt;
    We&#039;ve turned up .tel registrations now that they&#039;ve gone realtime and the initial registry implosion has stabilized. You may have noticed a distinct lack of urgency from us to light a fire under your keester to go register your name under .tel &lt;b&gt;right now&lt;/b&gt; before somebody &lt;i&gt;else&lt;/i&gt; takes it.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
As we outlined &lt;a href=&quot;http://blog.easydns.org/archives/219-.ME-Top-Level-Domain-launch-indicative-of-new-TLD-rollouts.html&quot;&gt;previously&lt;/a&gt;, we find the hoopla around new top-level domain rollouts both tiresome and for the majority of domain holders, unnecessary. So we have a policy here that we generally a) don&#039;t launch the new TLD until it goes realtime and is considered &quot;stable&quot; and b) we don&#039;t try to whip our users into a hysterical frenzy ahead of time to register their domains under every new TLD.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
The fact is, in the future there will be more top-level-domains, a lot more. So many of them that between obvious typos of one&#039;s domain, one&#039;s core domain or domains, and one&#039;s local geographic top-level domain, it will be a fool&#039;s errand to try and register your name under every new TLD that comes along just for the sake of &quot;defending your mark&quot;.&lt;br /&gt;&lt;br /&gt;&lt;h4&gt;The other problem is, .tel is severely crippled&lt;/h4&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
While we do find .tel slightly unique in the realm of new TLDs because it actually exists for a reason: to cultivate internet telephony usage. This isn&#039;t some country-code ccTLD hiring out their namespace under some made-up reason (.me, .tv, .ws, et al) to draw in foreign registrants, it&#039;s an actual TLD geared toward SIP, VOIP and telephony and exists for that reason.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
But .tel isn&#039;t doing anything under the space that can&#039;t be done under any other domain name with the appropriate use of SRV or NAPTR records and to actually make matters worse, you are forced to use their nameservers and your domains are under an Acceptable Use Policy which forces you to use the name for certain things (basically as a &quot;contact&quot; switch rather than a &quot;content&quot; page).&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
While the objective may be laudable: giving a TLD an actual raison d&#039;etre beyond &quot;register your name before somebody else does!&quot;, we don&#039;t like that you&#039;re forced to use their nameservers and don&#039;t have total latitude with your .tel domains. It runs contrary to the ethos behind easyDNS which was, and still is to drive a stake through the heart of lock-in. (It&#039;s not like we force everybody who registers a domain through us to use our nameservers because we&#039;re an outsourced DNS host, in fact we even allow our members to mirror their DNS from our nameservers from outside DNS hosts).&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
As such we have not become directly accredited under .tel, instead we&#039;re supporting them through our OpenSRS reseller tag, but the functionality is transparent.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
Most of you reading this probably have no compelling reason to register your name under .tel unless 1) you like the TLD or 2) you have operations in the IP telephony space that would make sense segmenting under a .tel name and 3) you don&#039;t mind the crippled functionality and lock-in. &lt;br /&gt;
     
    </content:encoded>

    <pubDate>Tue, 31 Mar 2009 11:50:00 -0400</pubDate>
    <guid isPermaLink="false">http://www.privateworld.com/archives/209-guid.html</guid>
    
</item>
<item>
    <title>New easyDNS Member feedback survey</title>
    <link>http://www.privateworld.com/archives/206-New-easyDNS-Member-feedback-survey.html</link>
            <category>via easyDNS blog</category>
    
    <comments>http://www.privateworld.com/archives/206-New-easyDNS-Member-feedback-survey.html#comments</comments>
    <wfw:comment>http://www.privateworld.com/wfwcomment.php?cid=206</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.privateworld.com/rss.php?version=2.0&amp;type=comments&amp;cid=206</wfw:commentRss>
    

    <author>nospam@example.com (easyDNS: of Interest)</author>
    <content:encoded>
    &lt;br /&gt;
    Many of you may not know that we have an ongoing member feedback survey where we ask for your thoughts and impressions of using easyDNS.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
We try to make it as unobtrusive as possible, and for each respondent we make a $5 donation to a charity of your choosing (World Wildlife Fund, Children&#039;s Wish Fund or Unicef).&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
We&#039;ve recoded the survey using &lt;a href=&quot;http://www.esurveys.com&quot; target=&quot;new&quot;&gt;eSurveys.com&lt;/a&gt;. Feel free to give us your thoughts by &lt;a href=&quot;http://www.easydns.com/feedback.php&quot;&gt;taking it today&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;&lt;a href=&quot;http://www.easydns.com/feedback.php&quot;&gt;easyDNS Member Survey&lt;/a&gt; 
    </content:encoded>

    <pubDate>Wed, 11 Mar 2009 16:13:31 -0400</pubDate>
    <guid isPermaLink="false">http://www.privateworld.com/archives/206-guid.html</guid>
    
</item>
<item>
    <title>Why we do not offer Whois Privacy at easyDNS</title>
    <link>http://www.privateworld.com/archives/193-Why-we-do-not-offer-Whois-Privacy-at-easyDNS.html</link>
            <category>via easyDNS blog</category>
    
    <comments>http://www.privateworld.com/archives/193-Why-we-do-not-offer-Whois-Privacy-at-easyDNS.html#comments</comments>
    <wfw:comment>http://www.privateworld.com/wfwcomment.php?cid=193</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.privateworld.com/rss.php?version=2.0&amp;type=comments&amp;cid=193</wfw:commentRss>
    

    <author>nospam@example.com (easyDNS: of Interest)</author>
    <content:encoded>
    &lt;br /&gt;
    We get asked this a alot: Why do you guys not offer whois masking or whois contact privacy?&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
The brief background on this is: whenever you register a domain name, your contact details are published in a publicly visible database called &quot;whois&quot;, where your contact details are instantly harvested by spambots and marketers who proceed to email and postal mail you marketing offers, deceptive &quot;domain slamming&quot; attempts, ads for dubious products, and perhaps even telemarketing calls.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
Nobody likes that, so over the years people started resorting to various tactics to protect themselves from the deluge of crap that inevitably comes with simply registering a domain name: throwaway email addresses in whois records, fake postal addresses, fake phone numbers, etc. The problem is, Registrants are obligated under their various end user agreements to provide true and accurate data (not doing so is grounds to lose one&#039;s domain), and the US even passed legislation making it unlawful to use fake contact details in a domain name registration.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
Our response to this, years ago, was &lt;a href=&quot;http://www.myprivacy.ca&quot;&gt;MyPrivacy.ca&lt;/a&gt; which protects your email address from being harvested from your whois records, but leaves your other data intact. We didn&#039;t see it as a revenue opportunity, in fact we made it free and opened it up to competing registrars, many of whom started recommending it to their customers. We just wanted to drive a stake through the heart of the whois spammers.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
It wasn&#039;t long though, before many registrars took it a step further and created the concept of &quot;whois masking&quot; or &quot;contact privacy&quot;, where all of the domain-holder contact details would be masked from the public whois. Of course, this was heralded as a &quot;value-add&quot; and most outfits charge extra for it.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
In today&#039;s long overdue post, we&#039;re finally revealing why so-called &quot;whois privacy&quot; puts your domains at risk, costs you more and doesn&#039;t really protect your privacy.&lt;br /&gt;&lt;br /&gt;&lt;a href=&quot;http://blog.easydns.org/archives/247-Why-we-do-not-offer-Whois-Privacy-at-easyDNS.html#extended&quot;&gt;Continue reading &quot;Why we do not offer Whois Privacy at easyDNS&quot;&lt;/a&gt; 
    </content:encoded>

    <pubDate>Thu, 20 Nov 2008 11:29:13 -0500</pubDate>
    <guid isPermaLink="false">http://www.privateworld.com/archives/193-guid.html</guid>
    
</item>
<item>
    <title>Why we do not offer Whois masking at easyDNS</title>
    <link>http://www.privateworld.com/archives/194-Why-we-do-not-offer-Whois-masking-at-easyDNS.html</link>
            <category>via easyDNS blog</category>
    
    <comments>http://www.privateworld.com/archives/194-Why-we-do-not-offer-Whois-masking-at-easyDNS.html#comments</comments>
    <wfw:comment>http://www.privateworld.com/wfwcomment.php?cid=194</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.privateworld.com/rss.php?version=2.0&amp;type=comments&amp;cid=194</wfw:commentRss>
    

    <author>nospam@example.com (easyDNS: of Interest)</author>
    <content:encoded>
    &lt;br /&gt;
    We get asked this a alot: Why do you guys not offer whois masking or whois contact privacy?&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
The brief background on this is: whenever you register a domain name, your contact details are published in a publicly visible database called &quot;whois&quot;, where your contact details are instantly harvested by spambots and marketers who proceed to email and postal mail you marketing offers, deceptive &quot;domain slamming&quot; attempts, ads for dubious products, and perhaps even telemarketing calls.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
Nobody likes that, so over the years people started resorting to various tactics to protect themselves from the deluge of crap that inevitably comes with simply registering a domain name: throwaway email addresses in whois records, fake postal addresses, fake phone numbers, etc. The problem is, Registrants are obligated under their various end user agreements to provide true and accurate data (not doing so is grounds to lose one&#039;s domain), and the US even passed legislation making it unlawful to use fake contact details in a domain name registration.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
Our response to this, years ago, was &lt;a href=&quot;http://www.myprivacy.ca&quot;&gt;MyPrivacy.ca&lt;/a&gt; which protects your email address from being harvested from your whois records, but leaves your other data intact. We didn&#039;t see it as a revenue opportunity, in fact we made it free and opened it up to competing registrars, many of whom started recommending it to their customers. We just wanted to drive a stake through the heart of the whois spammers.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
It wasn&#039;t long though, before many registrars took it a step further and created the concept of &quot;whois masking&quot; or &quot;contact privacy&quot;, where all of the domain-holder contact details would be masked from the public whois. Of course, this was heralded as a &quot;value-add&quot; and most outfits charge extra for it.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
In today&#039;s long overdue post, we&#039;re finally revealing why so-called &quot;whois privacy&quot; puts your domains at risk, costs you more and doesn&#039;t really protect your privacy.&lt;br /&gt;&lt;br /&gt;&lt;a href=&quot;http://blog.easydns.org/archives/247-Why-we-do-not-offer-Whois-masking-at-easyDNS.html#extended&quot;&gt;Continue reading &quot;Why we do not offer Whois masking at easyDNS&quot;&lt;/a&gt; 
    </content:encoded>

    <pubDate>Thu, 20 Nov 2008 11:29:13 -0500</pubDate>
    <guid isPermaLink="false">http://www.privateworld.com/archives/194-guid.html</guid>
    
</item>
<item>
    <title>MobileMe and easyDNS...</title>
    <link>http://www.privateworld.com/archives/190-MobileMe-and-easyDNS....html</link>
            <category>via easyDNS blog</category>
    
    <comments>http://www.privateworld.com/archives/190-MobileMe-and-easyDNS....html#comments</comments>
    <wfw:comment>http://www.privateworld.com/wfwcomment.php?cid=190</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.privateworld.com/rss.php?version=2.0&amp;type=comments&amp;cid=190</wfw:commentRss>
    

    <author>nospam@example.com (easyDNS: Tips and Tricks)</author>
    <content:encoded>
    &lt;br /&gt;
    A number of customers have been registering domains to point to their new websites published via iWeb on their MobileMe accounts. Unfortunately, while MobileMe instructs how to point &quot;www.yourdomain.com&quot; to their services, they don&#039;t have a way to easily point just &quot;yourdomain.com&quot; to their services. This is especially important as not everyone on the internet will type &quot;www&quot; before a domain name when looking for a website (such as &quot;www.google.com&quot; versus &quot;google.com&quot;).&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
Realising this is an issue for some of our customers who have DNS-Only services, we have implemented a work around. Simply follow the instructions on MobileMe to have your &quot;www.yourdomain.com&quot; CNAME point to &quot;web.me.com&quot;. These are correct, and are very important. However, one last step is to leave your &quot;yourdomain.com&quot; record in the &quot;hosts&quot; block pointing to the word &quot;PENDING&quot;. It should look something like this:&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;A record (host):&lt;/strong&gt;  yourdomain.com&lt;br /&gt;&lt;strong&gt;Has IP:&lt;/strong&gt;  PENDING&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
...with your CNAME looking like this:&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;C name (alias):&lt;/strong&gt;  www.yourdomain.com&lt;br /&gt;&lt;strong&gt;Points to A record (host):&lt;/strong&gt;  web.me.com&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
Once entered, click &quot;next&quot; to submit your changes, and &quot;next&quot; again after you have confirmed all looks well. These updates may take a few hours to propagate across the internet before you can see them.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
If you have any questions at all, please contact our Support Dept., and we would be happy to assist you. &lt;br /&gt;
     
    </content:encoded>

    <pubDate>Thu, 06 Nov 2008 13:03:02 -0500</pubDate>
    <guid isPermaLink="false">http://www.privateworld.com/archives/190-guid.html</guid>
    
</item>
<item>
    <title>How to explain &quot;URLs&quot; so anybody can understand them</title>
    <link>http://www.privateworld.com/archives/188-How-to-explain-URLs-so-anybody-can-understand-them.html</link>
            <category>via easyDNS blog</category>
    
    <comments>http://www.privateworld.com/archives/188-How-to-explain-URLs-so-anybody-can-understand-them.html#comments</comments>
    <wfw:comment>http://www.privateworld.com/wfwcomment.php?cid=188</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.privateworld.com/rss.php?version=2.0&amp;type=comments&amp;cid=188</wfw:commentRss>
    

    <author>nospam@example.com (easyDNS: Tips and Tricks)</author>
    <content:encoded>
    &lt;br /&gt;
    One of our tech support guys just had a conversation with somebody who wanted &quot;to register the URL http://example.com/something.html&quot;, where example.com was already registered, the person couldn&#039;t understand why he couldn&#039;t have that URL with &quot;something.html&quot; after it.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
We&#039;ve heard variations of this one a lot. Like somebody who knows &quot;xyz.zz&quot; is taken &quot;but can I register &quot;www.xyz.zz?&quot;, no, you can&#039;t.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
The easiest way to explain a URL such as this one:&lt;br /&gt;&lt;br /&gt;&lt;font size=+1&gt;http://www.example.com/something.html&lt;/font&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
Is to think of it as HOW, then WHERE and finally WHAT:&lt;br /&gt;&lt;br /&gt;&lt;table cellspacing=5 cellpadding=5&gt;&lt;br /&gt;&lt;tr&gt;&lt;br /&gt;&lt;td valign=top&gt;&lt;b&gt;http://&lt;/b&gt;&lt;/td&gt;&lt;td valign=top align=left nowrap&gt;&amp;laquo; how?&lt;/td&gt;&lt;td&gt;The method we are going to use to retrieve or &quot;get to&quot; the document described by the URL. Common ones are &quot;http&quot; (Hyper-Text Transfer Protocol), you may also see &quot;ftp://&quot; or &quot;mailto:&quot;&lt;/td&gt;&lt;/tr&gt;&lt;br /&gt;&lt;tr&gt;&lt;td valign=top&gt;&lt;br /&gt;&lt;b&gt;www.example.com&lt;/b&gt;&lt;/td&gt;&lt;td valign=top align=left nowrap&gt;&amp;laquo; where?&lt;/td&gt;&lt;td&gt;This is the hostname of the server, somewhere on the internet, which is holding the document we actually want&lt;/td&gt;&lt;/tr&gt;&lt;br /&gt;&lt;tr&gt;&lt;td valign=top&gt;&lt;br /&gt;&lt;b&gt;/something.html&lt;/b&gt;&lt;/td&gt;&lt;td valign=top align=left nowrap&gt;&amp;laquo; what?&lt;/td&gt;&lt;td&gt;Finally, after we know what server we are looking for and how we&#039;re going to retrieve the document from it, we now specify exactly &lt;i&gt;which document&lt;/i&gt; we want off of the remote server.&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
Understand those three components and you basically have URLs down cold. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
Your web browser (firefox, safari, IE, Opera) is all about &quot;how&quot;, what protocols to use to pull all these documents over the web to your desktop.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
The web host is the &quot;what&quot; machine. It sits on a server and serves document after document to remote web browsers who send it requests.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
Something has to bridge the browser to the web host/server and that&#039;s the &quot;where&quot;, that&#039;s where DNS and domains come in, and that&#039;s primarily what we do here at easyDNS. We tell web browsers (and other client applications) the &quot;where&quot; aspect of retrieving and transmitting documents (the &quot;whats&quot;) across the internet. We do this via &quot;DNS lookups&quot; ...about a quarter billion times a day. &lt;br /&gt;
     
    </content:encoded>

    <pubDate>Tue, 28 Oct 2008 09:47:14 -0400</pubDate>
    <guid isPermaLink="false">http://www.privateworld.com/archives/188-guid.html</guid>
    
</item>
<item>
    <title>What part of &quot;blanket permission to download&quot; do Michael Moore's lawyers not get?</title>
    <link>http://www.privateworld.com/archives/199-What-part-of-blanket-permission-to-download-do-Michael-Moores-lawyers-not-get.html</link>
            <category>via easyDNS blog</category>
    
    <comments>http://www.privateworld.com/archives/199-What-part-of-blanket-permission-to-download-do-Michael-Moores-lawyers-not-get.html#comments</comments>
    <wfw:comment>http://www.privateworld.com/wfwcomment.php?cid=199</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.privateworld.com/rss.php?version=2.0&amp;type=comments&amp;cid=199</wfw:commentRss>
    

    <author>nospam@example.com (easyDNS: of Interest)</author>
    <content:encoded>
    &lt;br /&gt;
    Michael Moore released his latest film &lt;a href=&quot;http://www.slackeruprising.com&quot;&gt;Slacker Uprising&lt;/a&gt; for free, over the web (note: don&#039;t click on that link if you live outside of the US or Canada or his lawyers will yell at us again). On the download page for the film Mr. Moore has this to say:&lt;br /&gt;&lt;br /&gt;&lt;blockquote&gt;&lt;br /&gt;&quot;I&#039;m giving you my blanket permission to not only download it, but also to email it, burn it, and share it with anyone and everyone (in the U.S. and Canada only). I want you to use &#039;Slacker Uprising&#039; in any way you see fit to help with the election or to do the work that you do in your community. You can show my film in your local theater, your high school classroom, your college auditorium, your church, union hall or community center. You can have your friends and neighbors over to the house for a viewing. You can broadcast it on TV, on cable access, on regular channels or on the web. It&#039;s completely free -- I don&#039;t want to see a dime from this. And if you want, you can charge admission or ask for a donation if it&#039;s to raise money for a candidate, a voter drive, or for any non-profit or educational purpose. In other words -- it&#039;s yours!&quot;&lt;br /&gt;&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
So, why are his lawyers demanding we take action regarding a torrent posted on a DNS hosting client&#039;s website? We received the following takedown request via Fedex today: &lt;br /&gt;&lt;a href=&quot;http://blog.easydns.org/archives/231-What-part-of-blanket-permission-to-download-do-Michael-Moores-lawyers-not-get.html#extended&quot;&gt;Continue reading &quot;What part of &amp;quot;blanket permission to download&amp;quot; do Michael Moore&#039;s lawyers not get?&quot;&lt;/a&gt; 
    </content:encoded>

    <pubDate>Mon, 29 Sep 2008 17:30:00 -0400</pubDate>
    <guid isPermaLink="false">http://www.privateworld.com/archives/199-guid.html</guid>
    
</item>
<item>
    <title>What part of &quot;blanket permission to download&quot; do Michael Moore's lawyers not get?</title>
    <link>http://www.privateworld.com/archives/184-What-part-of-blanket-permission-to-download-do-Michael-Moores-lawyers-not-get.html</link>
            <category>via easyDNS blog</category>
    
    <comments>http://www.privateworld.com/archives/184-What-part-of-blanket-permission-to-download-do-Michael-Moores-lawyers-not-get.html#comments</comments>
    <wfw:comment>http://www.privateworld.com/wfwcomment.php?cid=184</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.privateworld.com/rss.php?version=2.0&amp;type=comments&amp;cid=184</wfw:commentRss>
    

    <author>nospam@example.com (easyDNS: of Interest)</author>
    <content:encoded>
    &lt;br /&gt;
    Michael Moore released his latest film &lt;a href=&quot;http://www.slackeruprising.com&quot;&gt;Slacker Uprising&lt;/a&gt; for free, over the web (note: don&#039;t click on that link if you live outside of the US or Canada or his lawyers will yell at us again). On the download page for the film Mr. Moore has this to say:&lt;br /&gt;&lt;br /&gt;&lt;blockquote&gt;&lt;br /&gt;&quot;I&#039;m giving you my blanket permission to not only download it, but also to email it, burn it, and share it with anyone and everyone (in the U.S. and Canada only). I want you to use &#039;Slacker Uprising&#039; in any way you see fit to help with the election or to do the work that you do in your community. You can show my film in your local theater, your high school classroom, your college auditorium, your church, union hall or community center. You can have your friends and neighbors over to the house for a viewing. You can broadcast it on TV, on cable access, on regular channels or on the web. It&#039;s completely free -- I don&#039;t want to see a dime from this. And if you want, you can charge admission or ask for a donation if it&#039;s to raise money for a candidate, a voter drive, or for any non-profit or educational purpose. In other words -- it&#039;s yours!&quot;&lt;br /&gt;&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
So, why are his lawyers demanding we take action regarding a torrent posted on a DNS hosting client&#039;s website? We received the following takedown request via Fedex today: &lt;br /&gt;&lt;a href=&quot;http://blog.easydns.org/archives/231-What-part-of-blanket-permission-to-download-do-Michael-Moores-lawyers-not-get.html#extended&quot;&gt;Continue reading &quot;What part of &amp;quot;blanket permission to download&amp;quot; do Michael Moore&#039;s lawyers not get?&quot;&lt;/a&gt; 
    </content:encoded>

    <pubDate>Mon, 29 Sep 2008 15:51:03 -0400</pubDate>
    <guid isPermaLink="false">http://www.privateworld.com/archives/184-guid.html</guid>
    
</item>
<item>
    <title>Running an affiliate program? Don't pay for sales you already had in the bag</title>
    <link>http://www.privateworld.com/archives/179-Running-an-affiliate-program-Dont-pay-for-sales-you-already-had-in-the-bag.html</link>
            <category>via easyDNS blog</category>
    
    <comments>http://www.privateworld.com/archives/179-Running-an-affiliate-program-Dont-pay-for-sales-you-already-had-in-the-bag.html#comments</comments>
    <wfw:comment>http://www.privateworld.com/wfwcomment.php?cid=179</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.privateworld.com/rss.php?version=2.0&amp;type=comments&amp;cid=179</wfw:commentRss>
    

    <author>nospam@example.com (easyDNS: Tips and Tricks)</author>
    <content:encoded>
    &lt;br /&gt;
    People have tried this on us so many times I figure it must still work in many cases so after the last one I decided to post a brief note about this. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
We run an affiliate program via Commission Junction, it pays $20 per new customer acquisition. We also come up first in all major search engines for our own name: &quot;easydns&quot;, &quot;easydns.com&quot;, &quot;www.easydns.com&quot;, and &quot;easyDNS Technologies Inc&quot;. Every online business probably comes up first in Google for their own name. (If you don&#039;t, you have larger problems and you should probably address those).&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
Here&#039;s what I consider, if not a &quot;black hat&quot; PPC technique, a grey one which we&#039;re not interested in because it costs us affiliate commissions on sales we would have gotten without the affiliate ever being involved. Here&#039;s how the scam works: &lt;br /&gt;&lt;a href=&quot;http://blog.easydns.org/archives/227-Running-an-affiliate-program-Dont-pay-for-sales-you-already-had-in-the-bag.html#extended&quot;&gt;Continue reading &quot;Running an affiliate program? Don&#039;t pay for sales you already had in the bag&quot;&lt;/a&gt; 
    </content:encoded>

    <pubDate>Wed, 27 Aug 2008 11:31:29 -0400</pubDate>
    <guid isPermaLink="false">http://www.privateworld.com/archives/179-guid.html</guid>
    
</item>
<item>
    <title>Ten Years of easyDNS</title>
    <link>http://www.privateworld.com/archives/175-Ten-Years-of-easyDNS.html</link>
            <category>via easyDNS blog</category>
    
    <comments>http://www.privateworld.com/archives/175-Ten-Years-of-easyDNS.html#comments</comments>
    <wfw:comment>http://www.privateworld.com/wfwcomment.php?cid=175</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.privateworld.com/rss.php?version=2.0&amp;type=comments&amp;cid=175</wfw:commentRss>
    

    <author>nospam@example.com (easyDNS: of Interest)</author>
    <content:encoded>
    &lt;br /&gt;
    10 years ago on this day, we removed the password block on easyDNS.com and sent out a couple of innocuous email announcements to the PHP and Mysql mailing lists announcing that we had developed a DNS management system using php and mysql and it was now open for business. We had three nameservers, 1 in our office (where the &quot;other server&quot;, that ran everything was), one downtown in somebody else&#039;s cage at 151 Front street, and some friends of ours in Buffalo who were running an email company called chek.com let us run a third nameserver on one of their servers. That was the initial setup of easyDNS... &lt;br /&gt;&lt;a href=&quot;http://blog.easydns.org/archives/225-Ten-Years-of-easyDNS.html#extended&quot;&gt;Continue reading &quot;Ten Years of easyDNS&quot;&lt;/a&gt; 
    </content:encoded>

    <pubDate>Thu, 31 Jul 2008 10:25:21 -0400</pubDate>
    <guid isPermaLink="false">http://www.privateworld.com/archives/175-guid.html</guid>
    
</item>

</channel>
</rss>