Greetings, On September 6th 2009 at 11:00pm EST the EasyDNS sysops team will be conducting a scheduled maintenance on the EasyDNS members interface. The work will last until September 7th 2009 at 3:00am EST. Barring complications or tweaks, our goal will be to complete work in a shorter period than we have allocated, but we’re […]
easyURL.net now CLOSED to general public
Our URL shortening service easyURL.net is now CLOSED to the general public. 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 utilities module click on enable easyURL.net and then you’re done. Happy shortening. […]
easyURL.net adds useless "easyFrame" to redirects.
Feeling left out of the web 2.0 “URL Shortener” hysteria, we’ve added a mostly useless “easyFrame”(tm) to the easyURL.net redirect service. The culmination of nearly two night’s worth of programming in front of the TV, and nearing 100 lines of PHP code, the easyFrame(tm) enables people to further perpetuate it’s marginal functionality via other social […]
members.easydns.com was slow
Greetings, We were having some difficulty keeping load times under control on our members interface today, located at members.easydns.com. We have rectified the issue for the moment and are working diligently to ensure that we don’t run into this trouble in the future.
DNS usage counts back: May numbers borked
We’ve re-enabled access to viewing your DNS query counts online. Unfortunately, the May numbers are out of whack: you’ll see a large spike in your query counts between May 12 and May 19 which is actually each day’s total carried forward and added to the next. This was due to a parser bug caused by […]
Whois Privacy brings a lawsuit down on Registrar
Following on our explanation of why we do not offer whois masking here at easyDNS, we note tonight that Registrar Namecheap has been sued “over cybersquatting claims for a domain name registered under the NameCheap whois privacy services”. As we outlined in our original article: Whoever is listed as the Registrant in the domain’s whois […]
