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

<rss version="0.91" >
<channel>
<title>easyDNS Blog</title>
<link>http://blog.easydns.org/</link>
<description>Happenings and observations from easyDNS</description>
<language>en</language>
<image>
        <url>http://blog.easydns.org/templates/default/img/s9y_banner_small.png</url>
        <title>RSS: easyDNS Blog - Happenings and observations from easyDNS</title>
        <link>http://blog.easydns.org/</link>
        <width>100</width>
        <height>21</height>
    </image>

<item>
    <title>DNS usage quotas: before you panic</title>
    <link>http://blog.easydns.org/archives/307-DNS-usage-quotas-before-you-panic.html</link>

    <description>
        I&#039;ve fielded a handful of queries from members about &lt;a href=&quot;http://blog.easydns.org/archives/306-Big-Changes-Coming-to-easyDNS.html&quot; target=&quot;_new&quot;&gt;the coming DNS usage quotas&lt;/a&gt;. Some have looked at the &quot;query usage&quot; links beside their domain names and are surprised at the numbers they are seeing.&lt;br /&gt;
&lt;br /&gt;
One thing to be aware of is that &lt;b&gt;we&#039;ve discovered that the January numbers were tabulated incorrectly and are too high&lt;/b&gt;. To gain a truer insight into your usage, look at the January 28th figure. We are currently running a process to fix up the stats to reflect actual usage and expect to have those online within the next couple of days.&lt;br /&gt;
&lt;br /&gt;
But I&#039;d like to take an opportunity to convey the following principles behind this to our member base:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;&lt;a href=&quot;http://blog.easydns.org/archives/307-DNS-usage-quotas-before-you-panic.html#extended&quot;&gt;Continue reading &quot;DNS usage quotas: before you panic&quot;&lt;/a&gt;
    </description>
</item>
<item>
    <title>Big Changes Coming to easyDNS</title>
    <link>http://blog.easydns.org/archives/306-Big-Changes-Coming-to-easyDNS.html</link>

    <description>
        We will soon be launching our new member interface, a ground up rewrite of the current &lt;a href=&quot;https://members.easydns.com&quot; target=&quot;_new&quot;&gt;members.easydns.com&lt;/a&gt; website. It has been a long time in coming, like all complex projects, it always goes over-budget and takes longer than expected.&lt;br /&gt;
&lt;br /&gt;
The current user interface works, but it&#039;s pretty stale. There are so many layers of upgrades, fixes and plugins underneath the UI you see when you log in, that it&#039;s hit the point of diminishing returns: every time we add a feature or commit a bugfix, it seems to break something else. Despite the fact that most people dislike change, especially user interface changes, it is time to move on to the next level for easyDNS.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
 &lt;br /&gt;&lt;a href=&quot;http://blog.easydns.org/archives/306-Big-Changes-Coming-to-easyDNS.html#extended&quot;&gt;Continue reading &quot;Big Changes Coming to easyDNS&quot;&lt;/a&gt;
    </description>
</item>
<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>

    <description>
        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. 
    </description>
</item>
<item>
    <title>Holiday Hours</title>
    <link>http://blog.easydns.org/archives/303-Holiday-Hours.html</link>

    <description>
        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;
 
    </description>
</item>
<item>
    <title>telephone support </title>
    <link>http://blog.easydns.org/archives/302-telephone-support.html</link>

    <description>
        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 
    </description>
</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>

    <description>
        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. 
    </description>
</item>
<item>
    <title>appsto.re, a niched URL shortener for iphone apps</title>
    <link>http://blog.easydns.org/archives/300-appsto.re,-a-niched-URL-shortener-for-iphone-apps.html</link>

    <description>
        The other day I stumbled across &lt;a href=&quot;http://appsto.re&quot;&gt;http://appsto.re&lt;/a&gt;, a DNS client domain which is a pretty useful specialized URL shortener for iPhone apps. &lt;br /&gt;
&lt;br /&gt;
A good example is easyDNS&#039; own iPhone app for &lt;a href=&quot;http://www.easywhois.com&quot;&gt;easyWhois&lt;/a&gt;. The iTunes URL is loooooooooooooong and cumbersome, and to be honest, I can&#039;t readily remember what shortened URL I created for it on &lt;a href=&quot;http://easyurl.net&quot;&gt;easyURL&lt;/a&gt; (I think maybe &lt;a href=&quot;http://easyurl.net/easyiphone&quot;&gt;http://easyurl.net/easyiphone&lt;/a&gt;?)&lt;br /&gt;
&lt;br /&gt;
Well with appsto.re, we know it&#039;s simply &lt;a href=&quot;http://appsto.re/easyWhois&quot;&gt;http://appsto.re/easyWhois&lt;/a&gt;, and you can view the info for any given app by using &lt;a href=&quot;http://appsto.re/info/easyWhois&quot;&gt;http://appsto.re/info/easyWhois&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
You can even create your own custom shortened URLs for any given iPhone app. &lt;br /&gt;
&lt;br /&gt;
The other interesting thing about appsto.re that distinguishes it from most of the other URL shorteners out there, is that it actually has a revenue model, since I imagine they can use affiliate links to redirect to the paid apps (sorry guys, our app is free).&lt;br /&gt;
 
    </description>
</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>

    <description>
        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. 
    </description>
</item>
<item>
    <title>ns3.easydns.org</title>
    <link>http://blog.easydns.org/archives/298-ns3.easydns.org.html</link>

    <description>
        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;
 
    </description>
</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>

    <description>
        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 
    </description>
</item>
<item>
    <title>ns3.easydns.org this morning</title>
    <link>http://blog.easydns.org/archives/296-ns3.easydns.org-this-morning.html</link>

    <description>
        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, 
    </description>
</item>
<item>
    <title>NS1.EASYDNS.COM IP Change.</title>
    <link>http://blog.easydns.org/archives/295-NS1.EASYDNS.COM-IP-Change..html</link>

    <description>
        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. 
    </description>
</item>
<item>
    <title>SOLVED: Hardware outage.</title>
    <link>http://blog.easydns.org/archives/293-SOLVED-Hardware-outage..html</link>

    <description>
        &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. 
    </description>
</item>
<item>
    <title>members interface offline</title>
    <link>http://blog.easydns.org/archives/294-members-interface-offline.html</link>

    <description>
        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. 
    </description>
</item>
<item>
    <title>URL forwarding issues... *RESOLVED*</title>
    <link>http://blog.easydns.org/archives/292-URL-forwarding-issues...-RESOLVED.html</link>

    <description>
        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. 
    </description>
</item>

</channel>
</rss>
