<?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>easyDNS Blog - Status</title>
    <link>http://blog.easydns.org/</link>
    <description>Happenings and observations from easyDNS</description>
    <dc:language>en</dc:language>
    <generator>Serendipity 1.2.1 - http://www.s9y.org/</generator>
    <pubDate>Fri, 08 Jan 2010 16:16:40 GMT</pubDate>

    <image>
        <url>http://blog.easydns.org/templates/default/img/s9y_banner_small.png</url>
        <title>RSS: easyDNS Blog - Status - Happenings and observations from easyDNS</title>
        <link>http://blog.easydns.org/</link>
        <width>100</width>
        <height>21</height>
    </image>

<item>
    <title>Heads-up; re-assigning IPs of remote1.easydns.com and remote2.easydns.com</title>
    <link>http://blog.easydns.org/archives/304-Heads-up;-re-assigning-IPs-of-remote1.easydns.com-and-remote2.easydns.com.html</link>
            <category>Status</category>
    
    <comments>http://blog.easydns.org/archives/304-Heads-up;-re-assigning-IPs-of-remote1.easydns.com-and-remote2.easydns.com.html#comments</comments>
    <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=304</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.easydns.org/rss.php?version=2.0&amp;type=comments&amp;cid=304</wfw:commentRss>
    

    <author>nospam@example.com (easyDNS Support)</author>
    <content:encoded>
    We are re-assigning the IP addresses for remote1.easydns.com and&lt;br /&gt;
remote2.easydns.com.  The changes will be as follows;&lt;br /&gt;
&lt;br /&gt;
     WAS&lt;br /&gt;
     remote1.easydns.com    216.246.59.66&lt;br /&gt;
     remote2.easydns.com    209.200.141.4&lt;br /&gt;
&lt;br /&gt;
     IS NOW&lt;br /&gt;
     remote1.easydns.com    205.234.220.154&lt;br /&gt;
     remote2.easydns.com    209.200.187.4&lt;br /&gt;
&lt;br /&gt;
This will not impact name service resolution, although if you are a secondary customer and are using a DNS server that can not accept netblock assignments into the ACL (MS DNS servers) you will have to change your configuration to reflect this move. 
    </content:encoded>

    <pubDate>Fri, 08 Jan 2010 11:16:40 -0500</pubDate>
    <guid isPermaLink="false">http://blog.easydns.org/archives/304-guid.html</guid>
    
</item>
<item>
    <title>Holiday Hours</title>
    <link>http://blog.easydns.org/archives/303-Holiday-Hours.html</link>
            <category>Status</category>
    
    <comments>http://blog.easydns.org/archives/303-Holiday-Hours.html#comments</comments>
    <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=303</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.easydns.org/rss.php?version=2.0&amp;type=comments&amp;cid=303</wfw:commentRss>
    

    <author>nospam@example.com (easyDNS Support)</author>
    <content:encoded>
    Our offices will be open for telephone support:&lt;br /&gt;
&lt;br /&gt;
Thursday December 24th, 8:30AM - 3:00PM&lt;br /&gt;
Friday December 25th, closed&lt;br /&gt;
Saturday December 26th, closed&lt;br /&gt;
Sunday December 27th, 12:00AM - 6:00PM&lt;br /&gt;
Monday December 28th, 10:00AM - 6:00PM&lt;br /&gt;
Thursday December 31st, 8:30AM - 3:00PM&lt;br /&gt;
Friday January 1st, closed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
thank you&lt;br /&gt;
easyDNS&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Tue, 22 Dec 2009 11:52:47 -0500</pubDate>
    <guid isPermaLink="false">http://blog.easydns.org/archives/303-guid.html</guid>
    
</item>
<item>
    <title>telephone support </title>
    <link>http://blog.easydns.org/archives/302-telephone-support.html</link>
            <category>Status</category>
    
    <comments>http://blog.easydns.org/archives/302-telephone-support.html#comments</comments>
    <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=302</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.easydns.org/rss.php?version=2.0&amp;type=comments&amp;cid=302</wfw:commentRss>
    

    <author>nospam@example.com (easyDNS Support)</author>
    <content:encoded>
    Telephone support will be unavailable on Saturday December 12th, 2009 and will resume Sunday December 13th, 2009. Email support at support@easydns.com and billing@easydns.com will still be available.&lt;br /&gt;
&lt;br /&gt;
We do apologise for the inconvenience.&lt;br /&gt;
&lt;br /&gt;
thank you&lt;br /&gt;
easyDNS 
    </content:encoded>

    <pubDate>Fri, 11 Dec 2009 15:00:30 -0500</pubDate>
    <guid isPermaLink="false">http://blog.easydns.org/archives/302-guid.html</guid>
    
</item>
<item>
    <title>Power outage at the Amsterdam co-lo...</title>
    <link>http://blog.easydns.org/archives/301-Power-outage-at-the-Amsterdam-co-lo....html</link>
            <category>Status</category>
    
    <comments>http://blog.easydns.org/archives/301-Power-outage-at-the-Amsterdam-co-lo....html#comments</comments>
    <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=301</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.easydns.org/rss.php?version=2.0&amp;type=comments&amp;cid=301</wfw:commentRss>
    

    <author>nospam@example.com (easyDNS Support)</author>
    <content:encoded>
    Just over an hour ago, the co-location facility we use in Amsterdam suffered a brief power outage, which resulted in two of our nameservers being unexpectedly restarted:&lt;br /&gt;
&lt;br /&gt;
ams1.easydns.com (part of the &quot;ns1.easydns.com&quot; Anycast cluster)&lt;br /&gt;
ns6.easydns.net&lt;br /&gt;
&lt;br /&gt;
Our sysAdmins took &quot;ams1.easydns.com&quot; out of the &quot;ns1.easydns.com&quot; Anycast cluster as soon as this occurred, which means that &quot;ns1.easydns.com&quot; was not affected at all. However, as &quot;ns6.easydns.net&quot; is currently a stand-alone nameserver, our sysAdmins focused on bring this server up as quickly as possible.&lt;br /&gt;
&lt;br /&gt;
At this time, &quot;ns6.easydns.net&quot; is operational again and responding to queries, and we will work with our co-location provider to determine the cause of this outage.&lt;br /&gt;
&lt;br /&gt;
We apologise for any inconvenience. 
    </content:encoded>

    <pubDate>Thu, 10 Dec 2009 12:43:25 -0500</pubDate>
    <guid isPermaLink="false">http://blog.easydns.org/archives/301-guid.html</guid>
    
</item>
<item>
    <title>If the ns3 problem is still causing you trouble, read this</title>
    <link>http://blog.easydns.org/archives/299-If-the-ns3-problem-is-still-causing-you-trouble,-read-this.html</link>
            <category>Status</category>
    
    <comments>http://blog.easydns.org/archives/299-If-the-ns3-problem-is-still-causing-you-trouble,-read-this.html#comments</comments>
    <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=299</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.easydns.org/rss.php?version=2.0&amp;type=comments&amp;cid=299</wfw:commentRss>
    

    <author>nospam@example.com (Mark Jeftovic)</author>
    <content:encoded>
    We&#039;ve changed the glue record in the roots for ns3.easydns.org to reference a different node while we debug the data syncing issue.&lt;br /&gt;
&lt;br /&gt;
Some queries are still coming in owing to DNS cache issues. If you recently updated your zone and that update has not been reflected in ns3.easydns.org then you could also consider removing ns3.easydns.org from your DNS delegation.&lt;br /&gt;
&lt;br /&gt;
ns3 is a stand-alone node (we will be phasing out the stand-alone noded in the new year), as long as you have the ns1 and ns2 anycast strands in your delegation, you can safely remove ns3 from the delegation. 
    </content:encoded>

    <pubDate>Mon, 07 Dec 2009 13:28:01 -0500</pubDate>
    <guid isPermaLink="false">http://blog.easydns.org/archives/299-guid.html</guid>
    
</item>
<item>
    <title>ns3.easydns.org</title>
    <link>http://blog.easydns.org/archives/298-ns3.easydns.org.html</link>
            <category>Status</category>
    
    <comments>http://blog.easydns.org/archives/298-ns3.easydns.org.html#comments</comments>
    <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=298</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.easydns.org/rss.php?version=2.0&amp;type=comments&amp;cid=298</wfw:commentRss>
    

    <author>nospam@example.com (easyDNS Support)</author>
    <content:encoded>
    We&#039;re experiencing issues with this machine updating zone info.&lt;br /&gt;
We are working to resolve this issue and will post further info as it becomes available.&lt;br /&gt;
&lt;br /&gt;
NS3 may become unresponsive for a brief period as we restart all DNS services on this machine.&lt;br /&gt;
&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Mon, 07 Dec 2009 10:21:58 -0500</pubDate>
    <guid isPermaLink="false">http://blog.easydns.org/archives/298-guid.html</guid>
    
</item>
<item>
    <title>Telephone Support - Sunday 6 December, 2009</title>
    <link>http://blog.easydns.org/archives/297-Telephone-Support-Sunday-6-December,-2009.html</link>
            <category>Status</category>
    
    <comments>http://blog.easydns.org/archives/297-Telephone-Support-Sunday-6-December,-2009.html#comments</comments>
    <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=297</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.easydns.org/rss.php?version=2.0&amp;type=comments&amp;cid=297</wfw:commentRss>
    

    <author>nospam@example.com (easyDNS Support)</author>
    <content:encoded>
    At this time, telephone support is not available.&lt;br /&gt;
&lt;br /&gt;
For support or billing inquiries, please email us:&lt;br /&gt;
&lt;br /&gt;
support@easydns.com&lt;br /&gt;
&lt;br /&gt;
billing@easydns.com&lt;br /&gt;
&lt;br /&gt;
Thank you,&lt;br /&gt;
&lt;br /&gt;
The easyDNS Support Team 
    </content:encoded>

    <pubDate>Sun, 06 Dec 2009 14:09:32 -0500</pubDate>
    <guid isPermaLink="false">http://blog.easydns.org/archives/297-guid.html</guid>
    
</item>
<item>
    <title>ns3.easydns.org this morning</title>
    <link>http://blog.easydns.org/archives/296-ns3.easydns.org-this-morning.html</link>
            <category>Status</category>
    
    <comments>http://blog.easydns.org/archives/296-ns3.easydns.org-this-morning.html#comments</comments>
    <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=296</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.easydns.org/rss.php?version=2.0&amp;type=comments&amp;cid=296</wfw:commentRss>
    

    <author>nospam@example.com (easyDNS Support)</author>
    <content:encoded>
    Greetings, &lt;br /&gt;
&lt;br /&gt;
  We are experiencing an issue with the DNS resolver on &lt;strong&gt;ns3.easydns.org&lt;/strong&gt; this morning.  This issue will not impact resolution.  We are currently working with our network provider in London to resolve this issue. &lt;br /&gt;
&lt;br /&gt;
Thanks, 
    </content:encoded>

    <pubDate>Sat, 05 Dec 2009 08:16:11 -0500</pubDate>
    <guid isPermaLink="false">http://blog.easydns.org/archives/296-guid.html</guid>
    
</item>
<item>
    <title>NS1.EASYDNS.COM IP Change.</title>
    <link>http://blog.easydns.org/archives/295-NS1.EASYDNS.COM-IP-Change..html</link>
            <category>Status</category>
    
    <comments>http://blog.easydns.org/archives/295-NS1.EASYDNS.COM-IP-Change..html#comments</comments>
    <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=295</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.easydns.org/rss.php?version=2.0&amp;type=comments&amp;cid=295</wfw:commentRss>
    

    <author>nospam@example.com (easyDNS Support)</author>
    <content:encoded>
    We are in the midst of changing the anycast address for ns1.easydns.com&lt;br /&gt;
The new IP of ns1 will be 64.68.192.10 , we are in the process if switching the zone entry as well as updating the glue records for ns1.easydns.com&lt;br /&gt;
&lt;br /&gt;
We will leave the old IP operational for a couple of weeks.&lt;br /&gt;
During this time both the new IP and old IP will respond to queries.&lt;br /&gt;
&lt;br /&gt;
As always, if you have any questions please do not hesitate to contact us. 
    </content:encoded>

    <pubDate>Thu, 03 Dec 2009 10:03:13 -0500</pubDate>
    <guid isPermaLink="false">http://blog.easydns.org/archives/295-guid.html</guid>
    
</item>
<item>
    <title>SOLVED: Hardware outage.</title>
    <link>http://blog.easydns.org/archives/293-SOLVED-Hardware-outage..html</link>
            <category>Status</category>
    
    <comments>http://blog.easydns.org/archives/293-SOLVED-Hardware-outage..html#comments</comments>
    <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=293</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.easydns.org/rss.php?version=2.0&amp;type=comments&amp;cid=293</wfw:commentRss>
    

    <author>nospam@example.com (easyDNS Support)</author>
    <content:encoded>
    &lt;em&gt;&lt;strong&gt;Update:&lt;/strong&gt; The hardware outage has been solved and the members interface is now back online.&lt;/em&gt;&lt;br /&gt;
&lt;br /&gt;
We have discovered a hardware issue with one of our DB servers.&lt;br /&gt;
This affects the usage of our main site and members area. Our sysadmins are on site and working to resolve the issue as soon as possible. &lt;br /&gt;
&lt;br /&gt;
We&#039;ll post further updates as info becomes available. 
    </content:encoded>

    <pubDate>Sat, 28 Nov 2009 08:27:20 -0500</pubDate>
    <guid isPermaLink="false">http://blog.easydns.org/archives/293-guid.html</guid>
    
</item>
<item>
    <title>members interface offline</title>
    <link>http://blog.easydns.org/archives/294-members-interface-offline.html</link>
            <category>Status</category>
    
    <comments>http://blog.easydns.org/archives/294-members-interface-offline.html#comments</comments>
    <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=294</wfw:comment>

    <slash:comments>1</slash:comments>
    <wfw:commentRss>http://blog.easydns.org/rss.php?version=2.0&amp;type=comments&amp;cid=294</wfw:commentRss>
    

    <author>nospam@example.com (Mark Jeftovic)</author>
    <content:encoded>
    The main easyDNS member&#039;s interface at https://members.easydns.com and public facing website are currently experiencing database communications issues and are offline.&lt;br /&gt;
&lt;br /&gt;
Systems personnel are onsite now and we hope to have things back to normal ASAP.&lt;br /&gt;
&lt;br /&gt;
In the meantime, easyDNS production systems - DNS, URL forwarding, email forwarding, etc. are unaffected.&lt;br /&gt;
&lt;br /&gt;
We will post updates accordingly and we are sorry for the outage. 
    </content:encoded>

    <pubDate>Sat, 28 Nov 2009 08:26:16 -0500</pubDate>
    <guid isPermaLink="false">http://blog.easydns.org/archives/294-guid.html</guid>
    
</item>
<item>
    <title>URL forwarding issues... *RESOLVED*</title>
    <link>http://blog.easydns.org/archives/292-URL-forwarding-issues...-RESOLVED.html</link>
            <category>Status</category>
    
    <comments>http://blog.easydns.org/archives/292-URL-forwarding-issues...-RESOLVED.html#comments</comments>
    <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=292</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.easydns.org/rss.php?version=2.0&amp;type=comments&amp;cid=292</wfw:commentRss>
    

    <author>nospam@example.com (easyDNS Support)</author>
    <content:encoded>
    Unfortunately, we are currently experiencing an issue with our URL forwarding services. Our sysAdmins are looking into the issue and hope to have it resolved as soon as possible.&lt;br /&gt;
&lt;br /&gt;
We apologise for the inconvenience.&lt;br /&gt;
&lt;br /&gt;
&lt;strong&gt;**UPDATE - 2009-11-12 - 12:02pm**&lt;/strong&gt;&lt;br /&gt;
The URL forwarding issue we were experiencing has been resolved, and the URL forwarding service is operational at this time. Again, we apologise for the inconvenience. 
    </content:encoded>

    <pubDate>Thu, 12 Nov 2009 10:45:32 -0500</pubDate>
    <guid isPermaLink="false">http://blog.easydns.org/archives/292-guid.html</guid>
    
</item>
<item>
    <title>Phone Support Is Not Available For The Rest Of The Day</title>
    <link>http://blog.easydns.org/archives/291-Phone-Support-Is-Not-Available-For-The-Rest-Of-The-Day.html</link>
            <category>Status</category>
    
    <comments>http://blog.easydns.org/archives/291-Phone-Support-Is-Not-Available-For-The-Rest-Of-The-Day.html#comments</comments>
    <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=291</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.easydns.org/rss.php?version=2.0&amp;type=comments&amp;cid=291</wfw:commentRss>
    

    <author>nospam@example.com (easyDNS Support)</author>
    <content:encoded>
    Hello,&lt;br /&gt;
&lt;br /&gt;
Due to continuing building maintenance we will not be able to provide phone support for the rest of today. &lt;br /&gt;
&lt;br /&gt;
If you have any questions or concerns, please email us:&lt;br /&gt;
&lt;br /&gt;
support@easydns.com &lt;br /&gt;
&lt;br /&gt;
billing@easydns.com&lt;br /&gt;
&lt;br /&gt;
Thanks!&lt;br /&gt;
&lt;br /&gt;
The easyDNS Team. 
    </content:encoded>

    <pubDate>Sun, 08 Nov 2009 15:10:08 -0500</pubDate>
    <guid isPermaLink="false">http://blog.easydns.org/archives/291-guid.html</guid>
    
</item>
<item>
    <title>Beware, Renewal Fraud.</title>
    <link>http://blog.easydns.org/archives/286-Beware,-Renewal-Fraud..html</link>
            <category>Status</category>
    
    <comments>http://blog.easydns.org/archives/286-Beware,-Renewal-Fraud..html#comments</comments>
    <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=286</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.easydns.org/rss.php?version=2.0&amp;type=comments&amp;cid=286</wfw:commentRss>
    

    <author>nospam@example.com (easyDNS Support)</author>
    <content:encoded>
    Our subscribers have brought to our attention a new email scam designed to transfer domain names away from their legitimate registrars.&lt;br /&gt;
Please be on the look out in your in box for a message from http://www.domainrenewal-online.org/ that will ask you to follow a link to renew your domain name.&lt;br /&gt;
This link has nothing to do with easyDNS and should be avoided if received.&lt;br /&gt;
&lt;br /&gt;
Thanks to our subscribers that have graciously brought this to our attention.,&lt;br /&gt;
&lt;br /&gt;
thank you&lt;br /&gt;
the easyDNS Team. 
    </content:encoded>

    <pubDate>Thu, 08 Oct 2009 16:22:07 -0400</pubDate>
    <guid isPermaLink="false">http://blog.easydns.org/archives/286-guid.html</guid>
    
</item>
<item>
    <title>Whois record modifications</title>
    <link>http://blog.easydns.org/archives/285-Whois-record-modifications.html</link>
            <category>Status</category>
    
    <comments>http://blog.easydns.org/archives/285-Whois-record-modifications.html#comments</comments>
    <wfw:comment>http://blog.easydns.org/wfwcomment.php?cid=285</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.easydns.org/rss.php?version=2.0&amp;type=comments&amp;cid=285</wfw:commentRss>
    

    <author>nospam@example.com (easyDNS Support)</author>
    <content:encoded>
    We are currently experiencing some difficulties with the members page whois modification module.&lt;br /&gt;
If you require an immediate whois record modification and are experiencing modification errors please contact our support department&lt;br /&gt;
at support@easydns.com &lt;br /&gt;
&lt;br /&gt;
we apologise for the inconvenience and hope for a speedy resolution&lt;br /&gt;
&lt;br /&gt;
thank you&lt;br /&gt;
easyDNS&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Wed, 07 Oct 2009 09:32:40 -0400</pubDate>
    <guid isPermaLink="false">http://blog.easydns.org/archives/285-guid.html</guid>
    
</item>

</channel>
</rss>