<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How to Port a Domain to the new easyDNS User Interface</title>
	<atom:link href="http://blog.easydns.org/2010/03/04/how-to-port-a-domain-to-the-new-easydns-user-interface/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.easydns.org/2010/03/04/how-to-port-a-domain-to-the-new-easydns-user-interface/</link>
	<description>Happenings and observations</description>
	<lastBuildDate>Wed, 01 Sep 2010 18:29:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: gramcito</title>
		<link>http://blog.easydns.org/2010/03/04/how-to-port-a-domain-to-the-new-easydns-user-interface/comment-page-1/#comment-220</link>
		<dc:creator>gramcito</dc:creator>
		<pubDate>Tue, 29 Jun 2010 19:51:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.easydns.org/archives/313-guid.html#comment-220</guid>
		<description>mass cutovers are something Rogers does and it creates headaches for users and admins (does anyone know anymore how/where to login to their &quot;rogers online account&quot;?).  So *thank you* for using a sane and simple approach and continuing to put into practice the solid network engineering principles which drew me to easyDNS in the first place.

I use the old interface a bit because it seems the new web UI has more javascript buglets with the strange old browsers I use and there are still a few broken links (search seems sporadic, a few missing help pages). Thanks for pushing out the new pages and leaving the old sold system in place so you and we can work out the bugs over the next few months.

You&#039;ve fixed DNS for me for years and now you are starting to fix SMTP too so one thing I&#039;d like a bit more information on is easySMTP. Why does the enable mailout option even appear in non DNS+Plus accounts. Is it included in DNS+Pro? Is there a charge if we turn it on? Can we pay to have our quota raised from 250 mails a day? Can we forward suggestions or &quot;user documentation&quot; for easySMTP (a wiki would be nice)?  I am trying to build out postfix servers that use DKIM/SPF/SASL/SMTP-AUTH and whatever other features I can put together (pgp signing/openssl encryption) to make e-mail an enterprise grade service like it was in the 1990s ;-)

I&#039;d like to help easyDNS help me to do that. 

Thanks a lot and cheers,

ps: ipv6!! thanks!
pps: I&#039;m pretty good with mediawiki if you want help with that.</description>
		<content:encoded><![CDATA[<p>mass cutovers are something Rogers does and it creates headaches for users and admins (does anyone know anymore how/where to login to their &#034;rogers online account&#034;?).  So *thank you* for using a sane and simple approach and continuing to put into practice the solid network engineering principles which drew me to easyDNS in the first place.</p>
<p>I use the old interface a bit because it seems the new web UI has more javascript buglets with the strange old browsers I use and there are still a few broken links (search seems sporadic, a few missing help pages). Thanks for pushing out the new pages and leaving the old sold system in place so you and we can work out the bugs over the next few months.</p>
<p>You&#039;ve fixed DNS for me for years and now you are starting to fix SMTP too so one thing I&#039;d like a bit more information on is easySMTP. Why does the enable mailout option even appear in non DNS+Plus accounts. Is it included in DNS+Pro? Is there a charge if we turn it on? Can we pay to have our quota raised from 250 mails a day? Can we forward suggestions or &#034;user documentation&#034; for easySMTP (a wiki would be nice)?  I am trying to build out postfix servers that use DKIM/SPF/SASL/SMTP-AUTH and whatever other features I can put together (pgp signing/openssl encryption) to make e-mail an enterprise grade service like it was in the 1990s <img src='http://blog.easydns.org/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>I&#039;d like to help easyDNS help me to do that. </p>
<p>Thanks a lot and cheers,</p>
<p>ps: ipv6!! thanks!<br />
pps: I&#039;m pretty good with mediawiki if you want help with that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Jeftovic</title>
		<link>http://blog.easydns.org/2010/03/04/how-to-port-a-domain-to-the-new-easydns-user-interface/comment-page-1/#comment-188</link>
		<dc:creator>Mark Jeftovic</dc:creator>
		<pubDate>Thu, 10 Jun 2010 19:08:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.easydns.org/archives/313-guid.html#comment-188</guid>
		<description>This was debated for a long time internally over the years (yes, years) leading up to this. As a company that deals primarily in providing continuity of infrastructure - mass cutovers like that are potential disasters. Combine that with the fact that most people don&#039;t like forced, flash cuts we decided the best way to do this was incrementally and in the most non-disruptive way possible.</description>
		<content:encoded><![CDATA[<p>This was debated for a long time internally over the years (yes, years) leading up to this. As a company that deals primarily in providing continuity of infrastructure &#8211; mass cutovers like that are potential disasters. Combine that with the fact that most people don&#039;t like forced, flash cuts we decided the best way to do this was incrementally and in the most non-disruptive way possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nuno Ferreira</title>
		<link>http://blog.easydns.org/2010/03/04/how-to-port-a-domain-to-the-new-easydns-user-interface/comment-page-1/#comment-186</link>
		<dc:creator>Nuno Ferreira</dc:creator>
		<pubDate>Wed, 09 Jun 2010 22:45:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.easydns.org/archives/313-guid.html#comment-186</guid>
		<description>The way things should have worked:
On a simpler way, i.e., domains should have been migrated automatically to the new interface.</description>
		<content:encoded><![CDATA[<p>The way things should have worked:<br />
On a simpler way, i.e., domains should have been migrated automatically to the new interface.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Donovan</title>
		<link>http://blog.easydns.org/2010/03/04/how-to-port-a-domain-to-the-new-easydns-user-interface/comment-page-1/#comment-178</link>
		<dc:creator>Donovan</dc:creator>
		<pubDate>Mon, 07 Jun 2010 15:30:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.easydns.org/archives/313-guid.html#comment-178</guid>
		<description>Thanks for the reply Mark, I&#039;ll drop you a line.

The porting problems were strange, eventually switched back to the old interface.  Will give it a try again soon.</description>
		<content:encoded><![CDATA[<p>Thanks for the reply Mark, I&#039;ll drop you a line.</p>
<p>The porting problems were strange, eventually switched back to the old interface.  Will give it a try again soon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Jeftovic</title>
		<link>http://blog.easydns.org/2010/03/04/how-to-port-a-domain-to-the-new-easydns-user-interface/comment-page-1/#comment-177</link>
		<dc:creator>Mark Jeftovic</dc:creator>
		<pubDate>Mon, 07 Jun 2010 14:54:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.easydns.org/archives/313-guid.html#comment-177</guid>
		<description>Hi Don, feel free to let us know what doesn&#039;t work for you on the new interface. One of the advantages of rolling this out is that we can actually make changes fairly quickly, and even push more
functionality back to the user level (like make a particular aspect subject to a user preference).

The new system and the old system push their data to the same array of nameservers, there is nothing in the new system that would slow down the old one, if the legacy interface is slow to sync, then it&#039;s some other issue. Can you open a support ticket with the details around that if you haven&#039;t already so we can take a look?

thx.

You can also email your thoughts on the interface directly, my email is markjr [at] you_know_what . com</description>
		<content:encoded><![CDATA[<p>Hi Don, feel free to let us know what doesn&#039;t work for you on the new interface. One of the advantages of rolling this out is that we can actually make changes fairly quickly, and even push more<br />
functionality back to the user level (like make a particular aspect subject to a user preference).</p>
<p>The new system and the old system push their data to the same array of nameservers, there is nothing in the new system that would slow down the old one, if the legacy interface is slow to sync, then it&#039;s some other issue. Can you open a support ticket with the details around that if you haven&#039;t already so we can take a look?</p>
<p>thx.</p>
<p>You can also email your thoughts on the interface directly, my email is markjr [at] you_know_what . com</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Donovan</title>
		<link>http://blog.easydns.org/2010/03/04/how-to-port-a-domain-to-the-new-easydns-user-interface/comment-page-1/#comment-176</link>
		<dc:creator>Donovan</dc:creator>
		<pubDate>Mon, 07 Jun 2010 14:17:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.easydns.org/archives/313-guid.html#comment-176</guid>
		<description>I have to admit,  I&#039;m disappointed with the new interface.  Sure, users always hate change, but as a developer, and a happy easyDNS customer, I personally expected something user friendly, intuitive and visually appealing.

Had problems porting some domains too.  It also seems like updates on the old system take longer to sync now?  

Other folks who I&#039;ve recommended easyDNS to are struggling with the new interface as well.</description>
		<content:encoded><![CDATA[<p>I have to admit,  I&#039;m disappointed with the new interface.  Sure, users always hate change, but as a developer, and a happy easyDNS customer, I personally expected something user friendly, intuitive and visually appealing.</p>
<p>Had problems porting some domains too.  It also seems like updates on the old system take longer to sync now?  </p>
<p>Other folks who I&#039;ve recommended easyDNS to are struggling with the new interface as well.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
