<?xml version="1.0" encoding="utf-8" ?>
<?xml-stylesheet href="/templates/default/atom.css" type="text/css" ?>

<feed 
   xmlns="http://www.w3.org/2005/Atom"
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/">
    <link href="http://blog.easydns.org/feeds/atom10.xml" rel="self" title="easyDNS Blog" type="application/atom+xml" />
    <link href="http://blog.easydns.org/"                        rel="alternate"    title="easyDNS Blog" type="text/html" />
    <link href="http://blog.easydns.org/rss.php?version=2.0"     rel="alternate"    title="easyDNS Blog" type="application/rss+xml" />
    <title type="html">easyDNS Blog</title>
    <subtitle type="html">Happenings and observations from easyDNS</subtitle>
    <icon>http://blog.easydns.org/templates/default/img/s9y_banner_small.png</icon>
    <id>http://blog.easydns.org/</id>
    <updated>2008-08-08T13:30:34Z</updated>
    <generator uri="http://www.s9y.org/" version="1.2.1">Serendipity 1.2.1 - http://www.s9y.org/</generator>
    <dc:language>en</dc:language>

    <entry>
        <link href="http://blog.easydns.org/archives/226-Mail-Delays.html" rel="alternate" title="Mail Delays" />
        <author>
            <name>easyDNS Support</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2008-08-06T19:05:27Z</published>
        <updated>2008-08-08T13:30:34Z</updated>
        <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=226</wfw:comment>
    
        <slash:comments>0</slash:comments>
        <wfw:commentRss>http://blog.easydns.org/rss.php?version=atom1.0&amp;type=comments&amp;cid=226</wfw:commentRss>
    
            <category scheme="http://blog.easydns.org/categories/4-Status" label="Status" term="Status" />
    
        <id>http://blog.easydns.org/archives/226-guid.html</id>
        <title type="html">Mail Delays</title>
        <content type="xhtml" xml:base="http://blog.easydns.org/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                One of our mail forwarders was experiencing issues with relaying mail this afternoon.<br />
The cause of the slowdown has been identified and the issue resolved. The machine is now emptying its mail queue.<br />
<br />
Mail will have been delayed up to a couple of hours.<br />
<br />
We appreciate your patience as we resolve this matter. As always if you have any questions please feel free to contact support. 
            </div>
        </content>
        
    </entry>
    <entry>
        <link href="http://blog.easydns.org/archives/225-Ten-Years-of-easyDNS.html" rel="alternate" title="Ten Years of easyDNS" />
        <author>
            <name>Mark Jeftovic</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2008-07-31T14:25:21Z</published>
        <updated>2008-08-04T16:11:37Z</updated>
        <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=225</wfw:comment>
    
        <slash:comments>6</slash:comments>
        <wfw:commentRss>http://blog.easydns.org/rss.php?version=atom1.0&amp;type=comments&amp;cid=225</wfw:commentRss>
    
            <category scheme="http://blog.easydns.org/categories/3-Of-Interest" label="Of Interest" term="Of Interest" />
    
        <id>http://blog.easydns.org/archives/225-guid.html</id>
        <title type="html">Ten Years of easyDNS</title>
        <content type="xhtml" xml:base="http://blog.easydns.org/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                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 "other server", that ran everything was), one downtown in somebody else'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... <br /><a href="http://blog.easydns.org/archives/225-Ten-Years-of-easyDNS.html#extended">Continue reading "Ten Years of easyDNS"</a>
            </div>
        </content>
        
    </entry>
    <entry>
        <link href="http://blog.easydns.org/archives/224-Is-my-ISP-patched-for-the-DNS-cache-poisoning-bug.html" rel="alternate" title="Is my ISP patched for the DNS cache poisoning bug?" />
        <author>
            <name>Mark Jeftovic</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2008-07-24T15:40:36Z</published>
        <updated>2008-07-24T15:40:36Z</updated>
        <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=224</wfw:comment>
    
        <slash:comments>0</slash:comments>
        <wfw:commentRss>http://blog.easydns.org/rss.php?version=atom1.0&amp;type=comments&amp;cid=224</wfw:commentRss>
    
            <category scheme="http://blog.easydns.org/categories/4-Status" label="Status" term="Status" />
    
        <id>http://blog.easydns.org/archives/224-guid.html</id>
        <title type="html">Is my ISP patched for the DNS cache poisoning bug?</title>
        <content type="xhtml" xml:base="http://blog.easydns.org/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                We're going to start an item here to try to keep track of the ISPs who are patched for the DNS cache poisoning bug. Most of our personal contacts are here in Canada so this list will likely be comprised largely of Canadian ISPs but as we get word on other big ones, we'll try to update them here.<br />
<br />
So far just a couple of items but one of them is major, so I post now...<br />
<table border=1 cellpadding=5><br />
<tr><td>ISP</td><td>Status</td><td>Comments</td></tr><br />
<tr><td><b>Bell Canada:</b></td><td>Patched</td><td>We've checked with their ops team</td></tr><br />
<tr><td><b>Egate.net / EgateDSL</b></td><td>Patched</td><td>A lot of non-Bell DSL users here</td></tr><br />
</table> 
            </div>
        </content>
        
    </entry>
    <entry>
        <link href="http://blog.easydns.org/archives/222-easyDNS-soft-launches-DNSresolvers.com.html" rel="alternate" title="easyDNS soft launches DNSresolvers.com" />
        <author>
            <name>Mark Jeftovic</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2008-07-24T00:59:48Z</published>
        <updated>2008-07-24T02:21:53Z</updated>
        <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=222</wfw:comment>
    
        <slash:comments>2</slash:comments>
        <wfw:commentRss>http://blog.easydns.org/rss.php?version=atom1.0&amp;type=comments&amp;cid=222</wfw:commentRss>
    
            <category scheme="http://blog.easydns.org/categories/9-Whats-New" label="What's New" term="What's New" />
    
        <id>http://blog.easydns.org/archives/222-guid.html</id>
        <title type="html">easyDNS soft launches DNSresolvers.com</title>
        <content type="xhtml" xml:base="http://blog.easydns.org/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                With the <a href="http://blog.easydns.org/archives/223-DNS-cache-poisoning-exploit-released.html">ramifications of the DNS cache poisoning bug</a> beginning to sink in and the first exploit code being published today, we are anticipating an accelerating number of queries from our members about this and what they can do to ensure their own DNS caching resolvers are safe to use.<br />
<br />
We can tell you about two public DNS resolver systems you can use. One external, one we just launched ourselves:<br />
<br />
<h3>OpenDNS: User friendly DNS lookups - with anti-phishing protection</h3><br />
We've never been in the DNS resolution or DNS resolving business. There are companies like <a href="http://www.opendns.com">OpenDNS</a> who are. We know the people who run this company, they are competent and knowledgeable and we consider their service safe. That said, they also provide protection against phishing domains and they do trap NXDOMAIN traffic. Yes, they do monetize failed lookups via a search suggestion page with PPC links, individual users do have the ability to turn this off.<br />
<br />
<h3>easyDNS launches DNSResolvers.com: no frills, pure DNS lookups - fully patched</h3><br />
<br />
Some of our members have expressed reservations around using any DNS resolver that "alters" the traffic in any way, including typos and non-existent domains. Which is good news for us, because we've done this so fast we haven't had time to build anything like that even if we wanted to. What we did want to do is provide a couple of DNS resolvers for use by our members (or anybody else) who just want to know they're using a system run by people who are actively following this situation and are proactively keeping their own resolvers and caching nameservers as secure as the protocol allows.<br />
<br />
With this in mind we've turned up <b>DNSresolvers.com</b> today. No website, no user interface, at the moment it's just a couple of resolvers with the latest security patches in place and that will continue to do so, open to use by anybody who wants. We have no idea where this will go, and it's not really an official easyDNS "service" per se. But we wanted to do something to give our members options.<br />
<br />
If you want to use DNSresolvers.com, the details are as follows:<br />
<br />
<code><br />
cache1.dnsresolvers.com -> 205.210.42.205<br />
cache2.dnsresolvers.com -> 66.207.199.44<br />
</code> 
            </div>
        </content>
        
    </entry>
    <entry>
        <link href="http://blog.easydns.org/archives/223-DNS-cache-poisoning-exploit-released.html" rel="alternate" title="DNS cache poisoning exploit released" />
        <author>
            <name>Simon Carr</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2008-07-24T00:52:51Z</published>
        <updated>2008-07-24T01:43:07Z</updated>
        <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=223</wfw:comment>
    
        <slash:comments>0</slash:comments>
        <wfw:commentRss>http://blog.easydns.org/rss.php?version=atom1.0&amp;type=comments&amp;cid=223</wfw:commentRss>
    
            <category scheme="http://blog.easydns.org/categories/5-Industry-Watch" label="Industry Watch" term="Industry Watch" />
    
        <id>http://blog.easydns.org/archives/223-guid.html</id>
        <title type="html">DNS cache poisoning exploit released</title>
        <content type="xhtml" xml:base="http://blog.easydns.org/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                Hi There,<br />
<br />
   There is a new DNS Cache poisoning disclosure that has been  inadvertently leaked before it was scheduled to be released by Dan <br />
Kaminsky (IOActive).   This is a very serious flaw in the DNS protocol that impacts caching resolvers, like the resolvers hosted at your <br />
service provider that help your workstation resolve IP addresses to domain names.<br />
<br />
   This bug does not directly impact authoritative name servers like the ones used to host your domain names at EasyDNS.  Our name servers do not <br />
request answers from external sources, and rely entirely on internal cache files to offer answers.   So for example, nobody will be able to change your IP information on our end.  That part of the bug is unfortunately located at the caching end.<br />
<br />
   That being said; this is still a serious flaw, and we are taking this opportunity to upgrade the DNS software on our authoritative name servers to ensure that we are 100% compatible across the board with the newly upgraded caching name servers located at your Internet Service Provider.  These upgrades should not impact name resolution if you are using more than one of our name servers to serve answers for your domain name (actually, please ensure that you are).<br />
<br />
   To make sure your Internet Service Provider is up to speed, you can use <a href="http://www.doxpara.com/" title="DoxPora">Dan Kaminsky's  test script at DoxPora Research</a>.  If your Internet Service Provider is not yet up to speed, you may want to give them a nudge and/or change your DNS resolver configuration to a more trusted service.<br />
<br />
<b>Update</b> It is now <a href="http://www.circleid.com/posts/87233_dns_attack_code_published/">making news that an exploit to this attack has been released.</a>, please see our post about <a href="http://blog.easydns.org/archives/222-easyDNS-soft-launches-DNSresolvers.com.html">our newly launched DNSresolvers.com</a> if you are looking for safe resolvers.<br />
 
            </div>
        </content>
        
    </entry>
    <entry>
        <link href="http://blog.easydns.org/archives/220-RESOLVED-Duplicate-emails-being-relayed....html" rel="alternate" title="RESOLVED: Duplicate emails being relayed..." />
        <author>
            <name>easyDNS Support</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2008-07-22T15:27:56Z</published>
        <updated>2008-07-22T20:21:14Z</updated>
        <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=220</wfw:comment>
    
        <slash:comments>0</slash:comments>
        <wfw:commentRss>http://blog.easydns.org/rss.php?version=atom1.0&amp;type=comments&amp;cid=220</wfw:commentRss>
    
            <category scheme="http://blog.easydns.org/categories/4-Status" label="Status" term="Status" />
    
        <id>http://blog.easydns.org/archives/220-guid.html</id>
        <title type="html">RESOLVED: Duplicate emails being relayed...</title>
        <content type="xhtml" xml:base="http://blog.easydns.org/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                The issue we were experiencing previously with duplicate emails has been resolved. Customers may receive yet one more copy of the duplicate emails as our queues clear out.<br />
<br />
Please contact Support if you continue to experience this issue: support@easydns.com<br />
<br />
We apologise for any inconvenience. 
            </div>
        </content>
        
    </entry>
    <entry>
        <link href="http://blog.easydns.org/archives/219-.ME-Top-Level-Domain-launch-indicative-of-new-TLD-rollouts.html" rel="alternate" title=".ME Top Level Domain launch indicative of new TLD rollouts" />
        <author>
            <name>Mark Jeftovic</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2008-07-17T11:52:00Z</published>
        <updated>2008-07-18T12:10:20Z</updated>
        <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=219</wfw:comment>
    
        <slash:comments>0</slash:comments>
        <wfw:commentRss>http://blog.easydns.org/rss.php?version=atom1.0&amp;type=comments&amp;cid=219</wfw:commentRss>
    
            <category scheme="http://blog.easydns.org/categories/5-Industry-Watch" label="Industry Watch" term="Industry Watch" />
    
        <id>http://blog.easydns.org/archives/219-guid.html</id>
        <title type="html">.ME Top Level Domain launch indicative of new TLD rollouts</title>
        <content type="xhtml" xml:base="http://blog.easydns.org/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                We've gotten a few invitations to apply to be a .ME top-level domain registrar, to which we assigned no urgency after we took a straw poll internally and found that pretty well <b>zero</b> of our customers were asking for it. Today, Techcrunch reports that the <a href="http://www.techcrunch.com/2008/07/17/godaddys-domain-registration-totally-screws-me/"> .ME landrush, at least through one large operator, had degraded into a fracas.</a> We have an unwritten policy here: new Top Level Domain roll outs are to be avoided until they i) get past sunrise without erupting into a malestrom of lawsuits and ii) get past "go-live" without imploding.<br />
<br />
It runs contrary to industry standards where registrars whip their customer base into a frenzy over an exaggerated need to protect one's trademarks and claim one's stake in the latest "must have" TLD. The fact is, all you really need to care about are .COM, .NET and .ORG plus the ccTLD of the country you live in or do a lot of business in. (I will probably catch flack for saying .BIZ and .INFO are not crucial must-haves to your domain portfolio - we grabbed ours, at considerable expense in the case of .INFO and it was our experience in the roll out of these two that largely formed our policy.)<br />
<br />
That most of these new TLDs roll out with initial 2-year registration period minimums are just an outright cash grab from the registry that most participating registrars are happy to join in on. They know that the sunrise and landrush frenzies they hope to whip up are the single greatest revenue events these TLDs ever experience. After the hoopla dies off and organizations realize how unimportant owning say ".ZX" is in their overall domain strategy and the domainers who piled in find out the aftermarket for the TLD is lackluster at best, the renewal rates predictably fall off a cliff.<br />
<br />
So when the next "must have" TLD comes along and participating registrars start lovebombing their customers with reasons why they absolutely <i>must</i> "protect their name" in the new TLD, we often commit the egregious sin among investment bankers, VC's and pundits - that of "leaving money on the table" and we just don't rush in and push the new TLD. If it prevents us from leading our members off a ciff in to a major debacle, we consider ourselves as having done our job. (This was a similar rationale to why we never entered the IDN space, as long as you need a browser plug-in to make internationalized domain names even borderline usable they are, in our opinion, of marginal utility - we stayed out of it)<br />
<br />
This is in line with our lifelong strategy of cultivating members who actually <i>use</i> their domains rather than pushing the "get your name before its gone" angle for every TLD under the sun on anybody who can fog a mirror. When we launched back in '98, we couldn't even register domains at all, so our member base was exclusively people who were actively using their domains and wanted outsourced DNS and/or forwarding. That set the tone for our positioning and culture ever since, and while now we do have a lot of customers using us "as registrar", our core is always the active domain users. <br />
<br />
We have almost zero "domainers" with large portfolios of parked domains and speculative registrations because our model simply doesn't work for those types of users. It's not a judgement against domainers, it's just not where we came from.<br />
<br />
<br />
All that said, you would probably think we are opposed to the new "free-for-all" TLD expansion policy hinted to in the recent ICANN meeting in Paris. We are not. We would welcome this new tlds policy (if it ever actually happens) because it removes the artifical scarcity and counteracts that "cashgrab" mentality we sniff at the root of many a new TLD. If new TLDs are coming out all over the place, two things happen:<br />
<br />
1) Organizations realize that it is no longer practical to attempt to "protect their name" in every TLD space, so they stop trying. This removes a lot of the "easy money" underwriting new TLDs, some of which would otherwise launch for the thinly disguised reason of trying to milk the Sunrise for all its worth.<br />
<br />
2) The above impetus gone, new TLDs will have to compete in a much more open market. Registries, while having de facto localized monopolies within their own TLDs will have to provide actual value to compete with other TLDs.<br />
<br />
That appeals to our sense of market freedom: less artificial barriers compelling a drive toward providing more value and benefits. The winners in the end should be the domain registrants, who are, let's not forget, our customers.<br />
 
            </div>
        </content>
        
    </entry>
    <entry>
        <link href="http://blog.easydns.org/archives/218-EasyDNS-main-site-outage.html" rel="alternate" title="EasyDNS main site outage" />
        <author>
            <name>easyDNS Support</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2008-07-14T04:51:40Z</published>
        <updated>2008-07-14T05:11:34Z</updated>
        <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=218</wfw:comment>
    
        <slash:comments>0</slash:comments>
        <wfw:commentRss>http://blog.easydns.org/rss.php?version=atom1.0&amp;type=comments&amp;cid=218</wfw:commentRss>
    
            <category scheme="http://blog.easydns.org/categories/4-Status" label="Status" term="Status" />
    
        <id>http://blog.easydns.org/archives/218-guid.html</id>
        <title type="html">EasyDNS main site outage</title>
        <content type="xhtml" xml:base="http://blog.easydns.org/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                Greetings, <br />
<br />
  At approximately 6:00pm on Sunday July 13th, the hosting provider for a large part of our infrastructure experienced a partial power failure, causing a lot of our backend switching and routing infrastructure to malfunction.<br />
<br />
  During this outage, the EasyDNS members site would have been inaccessible, as well as mail forwarding and web forwarding services.  The bulk of the outage lasted 20 minutes, with after-effects against some services lasting some hours after that.  <br />
<br />
<br />
<br />
  The web forwarding service outage lasted longer than anticipated due to an internal disagreement between several devices on who was directing the traffic.  Intermittent service would have lasted between the beginning of the outage to about 11:00pm.  As of this writing the service has been fully restored and the devices agree with each other again. <br />
<br />
  Because of our firm commitment to DNS uptime, our DNS infrastructure and domain name resolution were not impacted and no forwarded or backup MX mail was lost.   
            </div>
        </content>
        
    </entry>
    <entry>
        <link href="http://blog.easydns.org/archives/217-5-questions-for-YCombinators-Paul-Graham.html" rel="alternate" title="5 questions for YCombinator's Paul Graham" />
        <author>
            <name>Mark Jeftovic</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2008-07-08T15:44:00Z</published>
        <updated>2008-07-15T15:13:51Z</updated>
        <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=217</wfw:comment>
    
        <slash:comments>2</slash:comments>
        <wfw:commentRss>http://blog.easydns.org/rss.php?version=atom1.0&amp;type=comments&amp;cid=217</wfw:commentRss>
    
            <category scheme="http://blog.easydns.org/categories/12-Who-Uses-easyDNS" label="Who Uses easyDNS?" term="Who Uses easyDNS?" />
    
        <id>http://blog.easydns.org/archives/217-guid.html</id>
        <title type="html">5 questions for YCombinator's Paul Graham</title>
        <content type="xhtml" xml:base="http://blog.easydns.org/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                When we noticed YCombinator's Paul Graham was an easyDNS member we asked him to help us kick off a new format for the "Who Uses easyDNS" blog channel. Rather than just list off this company or that notable tech personality, we're conducting short interviews with them so we can all get a better idea what our membership is all about.<br />
<br />
Paul Graham is a champion of the LISP programming language, a prominent essayist and author of the book <b>Hackers and Painters</b> and a VC who who co-founded the seed-stage funder <a href="http://ycombinator.com">Y Combinator</a>. <br />
<br />
To date <b>Y Combinator</b> has funded 102 start-ups and are currently accepting applications for the winter round of fundings, see <a href="http://ycombinator.com/w2009.html">http://ycombinator.com/w2009.html</a><br />
<br />
Mark Jeftovic conducted this email interview with Paul Graham over June 2008.<br />
<br />
<b>MJ: Are you at all disappointed that the development platform of choice behind the Web 2.0 "explosion" was Ruby on Rails instead of Lisp?</b><br />
<br />
 <br /><a href="http://blog.easydns.org/archives/217-5-questions-for-YCombinators-Paul-Graham.html#extended">Continue reading "5 questions for YCombinator's Paul Graham"</a>
            </div>
        </content>
        
    </entry>
    <entry>
        <link href="http://blog.easydns.org/archives/215-CIRA-implements-changes-to-the-dot-ca-WHOIS-search-tool..html" rel="alternate" title="CIRA implements changes to the dot-ca WHOIS search tool." />
        <author>
            <name>easyDNS Support</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2008-06-10T17:40:49Z</published>
        <updated>2008-06-10T17:40:49Z</updated>
        <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=215</wfw:comment>
    
        <slash:comments>0</slash:comments>
        <wfw:commentRss>http://blog.easydns.org/rss.php?version=atom1.0&amp;type=comments&amp;cid=215</wfw:commentRss>
    
            <category scheme="http://blog.easydns.org/categories/4-Status" label="Status" term="Status" />
    
        <id>http://blog.easydns.org/archives/215-guid.html</id>
        <title type="html">CIRA implements changes to the dot-ca WHOIS search tool.</title>
        <content type="xhtml" xml:base="http://blog.easydns.org/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                CIRA has implemented changes to the dot-ca WHOIS search tool, effective June 10, 2008.<br />
Domains that are registered to individuals now have their whois information kept private by default.<br />
For more information, please see http://www.cira.ca/en/Whois/whois_intro.html or contact us at support@easyDNS.com<br />
<br />
thank you,<br />
easyDNS 
            </div>
        </content>
        
    </entry>
    <entry>
        <link href="http://blog.easydns.org/archives/214-PayPal-Maintenace-Window.html" rel="alternate" title="PayPal Maintenace Window" />
        <author>
            <name>easyDNS Support</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2008-06-04T13:27:31Z</published>
        <updated>2008-06-04T13:27:31Z</updated>
        <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=214</wfw:comment>
    
        <slash:comments>0</slash:comments>
        <wfw:commentRss>http://blog.easydns.org/rss.php?version=atom1.0&amp;type=comments&amp;cid=214</wfw:commentRss>
    
            <category scheme="http://blog.easydns.org/categories/4-Status" label="Status" term="Status" />
    
        <id>http://blog.easydns.org/archives/214-guid.html</id>
        <title type="html">PayPal Maintenace Window</title>
        <content type="xhtml" xml:base="http://blog.easydns.org/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                On Tuesday, June 10th, and will start at 11 PM PDT and should last for approximately one hour.<br />
<br />
<br />
Here's what you should expect during the service interruption:<br />
<br />
· If you attempt to access the PayPal Web site (https://www.PayPal.com) during the maintenance window you will receive the following message:<br />
<br />
"The PayPal website is currently unavailable for scheduled maintenance. We are working actively to complete the maintenance as soon as possible. We apologize for any inconvenience. Please check the PayPal System Board for possible updates."<br />
<br />
You will be unable to log into the PayPal system to check your PayPal account status or to verify payments.<br />
<br />
You will be unable to send or receive funds via PayPal payment buttons on merchant sites or directly via the PayPal site.<br />
<br />
After the maintenance is complete, buyers and sellers will be able to interact with PayPal as they normally would.  
            </div>
        </content>
        
    </entry>
    <entry>
        <link href="http://blog.easydns.org/archives/211-IMPORTANT-Nouveau-politique-pour-les-fichiers-WHOIS-pour-les-domaines.html" rel="alternate" title="IMPORTANT : Nouveau politique pour les fichiers WHOIS pour les domaines" />
        <author>
            <name>Mark Jeftovic</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2008-05-30T19:40:00Z</published>
        <updated>2008-05-30T19:41:01Z</updated>
        <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=211</wfw:comment>
    
        <slash:comments>0</slash:comments>
        <wfw:commentRss>http://blog.easydns.org/rss.php?version=atom1.0&amp;type=comments&amp;cid=211</wfw:commentRss>
    
            <category scheme="http://blog.easydns.org/categories/11-Avis-aux-members" label="Avis aux members" term="Avis aux members" />
    
        <id>http://blog.easydns.org/archives/211-guid.html</id>
        <title type="html">IMPORTANT : Nouveau politique pour les fichiers WHOIS pour les domaines</title>
        <content type="xhtml" xml:base="http://blog.easydns.org/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                Ce que nos abonnés doivent savoir sur la nouvelle politique des domaine .Ca et au sujet  du Whois privée.<br />
<br />
A partir du Juin 10/2008 lACEI (l'Autorité Canadienne pour les Enregistrements Internet.) met en uvre un nouvelle politique Whois pour .CA qui touchera directement des Détenteurs de noms de domaine qui sont des particuliers (Titulaires), (à lopposition des Sociétés, entreprises ou des organismes au titre de Titulaires).<br />
<br />
Il est conseillé que tous nos Titulaires revisé la politique indiqué au: <br /><a href="http://blog.easydns.org/archives/211-IMPORTANT-Nouveau-politique-pour-les-fichiers-WHOIS-pour-les-domaines.html#extended">Continue reading "IMPORTANT : Nouveau politique pour les fichiers WHOIS pour les domaines"</a>
            </div>
        </content>
        
    </entry>
    <entry>
        <link href="http://blog.easydns.org/archives/213-PayPal-Maintenace-Window.html" rel="alternate" title="PayPal Maintenace Window" />
        <author>
            <name>easyDNS Support</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2008-05-30T13:43:45Z</published>
        <updated>2008-05-30T13:43:45Z</updated>
        <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=213</wfw:comment>
    
        <slash:comments>0</slash:comments>
        <wfw:commentRss>http://blog.easydns.org/rss.php?version=atom1.0&amp;type=comments&amp;cid=213</wfw:commentRss>
    
            <category scheme="http://blog.easydns.org/categories/4-Status" label="Status" term="Status" />
    
        <id>http://blog.easydns.org/archives/213-guid.html</id>
        <title type="html">PayPal Maintenace Window</title>
        <content type="xhtml" xml:base="http://blog.easydns.org/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                Update: The PayPal site maintenance scheduled for Thursday, May 29th at 11 PM PDT, has been postponed. We will update you once a new date has been confirmed.<br />
<br />
thank you<br />
easyDNS 
            </div>
        </content>
        
    </entry>
    <entry>
        <link href="http://blog.easydns.org/archives/212-IMPORTANT-New-.CA-Whois-Policy-takes-effect-June-102008.html" rel="alternate" title="IMPORTANT: New .CA Whois Policy takes effect June 10/2008" />
        <author>
            <name>Mark Jeftovic</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2008-05-28T17:52:46Z</published>
        <updated>2008-05-28T17:52:46Z</updated>
        <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=212</wfw:comment>
    
        <slash:comments>0</slash:comments>
        <wfw:commentRss>http://blog.easydns.org/rss.php?version=atom1.0&amp;type=comments&amp;cid=212</wfw:commentRss>
    
            <category scheme="http://blog.easydns.org/categories/10-Member-Mailouts" label="Member Mailouts" term="Member Mailouts" />
    
        <id>http://blog.easydns.org/archives/212-guid.html</id>
        <title type="html">IMPORTANT: New .CA Whois Policy takes effect June 10/2008</title>
        <content type="xhtml" xml:base="http://blog.easydns.org/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                What our subscribers need to know about the new .ca private whois service:<br />
<br />
On June 10/2008 CIRA is implementing a new .CA Whois policy which directly affects all .CA domains registered under the names of individuals<br />
(as opposed to .CA names registered to Corporations)<br />
<br />
It is advised that all .CA holders review the policy as outlined here: <br /><a href="http://blog.easydns.org/archives/212-IMPORTANT-New-.CA-Whois-Policy-takes-effect-June-102008.html#extended">Continue reading "IMPORTANT: New .CA Whois Policy takes effect June 10/2008"</a>
            </div>
        </content>
        
    </entry>
    <entry>
        <link href="http://blog.easydns.org/archives/210-PayPal-Maintenace-Window.html" rel="alternate" title="PayPal Maintenace Window" />
        <author>
            <name>easyDNS Support</name>
            <email>nospam@example.com</email>
        </author>
    
        <published>2008-05-15T15:09:44Z</published>
        <updated>2008-05-15T15:09:44Z</updated>
        <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=210</wfw:comment>
    
        <slash:comments>0</slash:comments>
        <wfw:commentRss>http://blog.easydns.org/rss.php?version=atom1.0&amp;type=comments&amp;cid=210</wfw:commentRss>
    
            <category scheme="http://blog.easydns.org/categories/4-Status" label="Status" term="Status" />
    
        <id>http://blog.easydns.org/archives/210-guid.html</id>
        <title type="html">PayPal Maintenace Window</title>
        <content type="xhtml" xml:base="http://blog.easydns.org/">
            <div xmlns="http://www.w3.org/1999/xhtml">
                On Thursday, May 29th, maintenance will start at 11 PM PDT and we expect it to last approximately one hour. <br />
<br />
Here's what you should expect during the service interruption: <br />
<br />
·        If you attempt to access the PayPal Web site (https://www.PayPal.com) during the maintenance window you will receive the following message: <br />
<br />
"The PayPal website is currently unavailable for scheduled maintenance.  We are working actively to complete the maintenance as soon as possible.  We apologize for any inconvenience.  Please check the PayPal System Board for possible updates."<br />
<br />
You will be unable to log into the PayPal system to check your PayPal account status or to verify payments.<br />
<br />
You will be unable to send or receive funds via PayPal payment buttons on merchant sites or directly via the PayPal site.<br />
<br />
After the maintenance is complete, buyers and sellers will be able to interact with PayPal as they normally would. <br />
 
            </div>
        </content>
        
    </entry>

</feed>