Comments on: EditGrid Add-ons go live! http://blog.editgrid.com/archives/74 everything about editgrid Thu, 21 Aug 2008 18:44:44 +0000 http://wordpress.org/?v=2.5.1 By: Justin http://blog.editgrid.com/archives/74#comment-1174 Justin Wed, 23 Aug 2006 14:30:25 +0000 http://blog.editgrid.com/archives/74#comment-1174 In case it helps, this is what I see on my end: Registrar of Record: REGISTERFLY.COM, INC. Record last updated on 22-Aug-2006. Record expires on 26-Oct-2007. Record created on 26-Oct-2005. Domain servers in listed order: NS0.XNAME.ORG 195.234.42.1 NS12.ZONEEDIT.COM 64.246.26.64 NS14.ZONEEDIT.COM 209.126.137.108 NS1.XNAME.ORG 193.218.105.149 I also use the free public dns servers on my end, but for lookups: 4.2.2.1 4.2.2.2 4.2.2.4 4.2.2.5 4.2.2.6 4.2.2.8 63.226.12.96 64.151.103.120 216.87.84.209 64.81.159.2 208.185.249.250 then I put our internal lan dns server in the last spot. What I've realized is that those free ones do speed things up really well from a desktop point of view, but when a site is down they serve up ads: http://kibosig.googlepages.com/editgridgoogledesktopsearchcache.html In case it helps, this is what I see on my end:

Registrar of Record: REGISTERFLY.COM, INC.
Record last updated on 22-Aug-2006.
Record expires on 26-Oct-2007.
Record created on 26-Oct-2005.

Domain servers in listed order:
NS0.XNAME.ORG 195.234.42.1
NS12.ZONEEDIT.COM 64.246.26.64
NS14.ZONEEDIT.COM 209.126.137.108
NS1.XNAME.ORG 193.218.105.149

I also use the free public dns servers on my end, but for lookups:
4.2.2.1
4.2.2.2
4.2.2.4
4.2.2.5
4.2.2.6
4.2.2.8
63.226.12.96
64.151.103.120
216.87.84.209
64.81.159.2
208.185.249.250
then I put our internal lan dns server in the last spot.

What I’ve realized is that those free ones do speed things up really well from a desktop point of view, but when a site is down they serve up ads:

http://kibosig.googlepages.com/editgridgoogledesktopsearchcache.html

]]> By: Justin http://blog.editgrid.com/archives/74#comment-1173 Justin Wed, 23 Aug 2006 14:17:11 +0000 http://blog.editgrid.com/archives/74#comment-1173 Ah, the perils of free as in beer and as in freedom. At least you guys are back up. You guys have a great application, even better than google spreadsheet and way better than irows. And ajaxXLS doesn't even have any security. Ah, the perils of free as in beer and as in freedom. At least you guys are back up. You guys have a great application, even better than google spreadsheet and way better than irows. And ajaxXLS doesn’t even have any security.

]]> By: Alan http://blog.editgrid.com/archives/74#comment-1171 Alan Tue, 22 Aug 2006 18:48:34 +0000 http://blog.editgrid.com/archives/74#comment-1171 The downtime is caused by failure in both nameservers at our upstream DNS hosting xname.org. We discovered the problem at around 14:00 UTC. After some troubleshooting to confirm failure from the nameservers, we decided to switch immediately to a temporary provider, zoneedit.com. By 14:30 UTC, we have already switched over the records at the domain registrar to the new nameservers. The migration process is a bit complicated and demanding. We managed to have recall from memory (in our brain) all the domain mappings that we have defined in the (unavailable) xname servers. Yet we finally did that, and did it quite nice. At around 15:30 UTC, we have noticed updated whois records being published by our registrar. At nearly the same time, one of our testers reported that they can access our domain. Unfortunately, due to the distributed design of the domain name system, there is simply no way for us to force every nameserver in the world to catch up the new records. That's why it may take some time for the records cached in your ISP to be updated. This is painful, yet unavoidable. We would like to express our sincere apology to any inconvinence that may have caused. We have been using DNS hosting service from xname.org for over 3 years. We believe that they are stable, however, we just discovered, after this incident, that their both nameservers are located in France, not as redundant as we originally thought. We will immediately devise better solutions to improve our DNS redundancy. We will try our best to make sure this will not happen again. By the time I submit this article, 1 of the 2 nameservers at xname have already recovered. I hope that everybody can access our service now. The downtime is caused by failure in both nameservers at our upstream DNS hosting xname.org. We discovered the problem at around 14:00 UTC. After some troubleshooting to confirm failure from the nameservers, we decided to switch immediately to a temporary provider, zoneedit.com. By 14:30 UTC, we have already switched over the records at the domain registrar to the new nameservers.

The migration process is a bit complicated and demanding. We managed to have recall from memory (in our brain) all the domain mappings that we have defined in the (unavailable) xname servers. Yet we finally did that, and did it quite nice. At around 15:30 UTC, we have noticed updated whois records being published by our registrar. At nearly the same time, one of our testers reported that they can access our domain.

Unfortunately, due to the distributed design of the domain name system, there is simply no way for us to force every nameserver in the world to catch up the new records. That’s why it may take some time for the records cached in your ISP to be updated. This is painful, yet unavoidable. We would like to express our sincere apology to any inconvinence that may have caused.

We have been using DNS hosting service from xname.org for over 3 years. We believe that they are stable, however, we just discovered, after this incident, that their both nameservers are located in France, not as redundant as we originally thought. We will immediately devise better solutions to improve our DNS redundancy. We will try our best to make sure this will not happen again.

By the time I submit this article, 1 of the 2 nameservers at xname have already recovered. I hope that everybody can access our service now.

]]> By: David Lee http://blog.editgrid.com/archives/74#comment-1167 David Lee Tue, 22 Aug 2006 18:19:19 +0000 http://blog.editgrid.com/archives/74#comment-1167 <p>I\'m terribly sorry for your inconvenience. We think it is unacceptable as well. Believe me, we have worked non-stop to get that fixed in the past few hours. We\'ll also do all we can do to prevent this from happening in the future.</p> <p>My colleague will explain what happened shortly afterward.</p> <p>My sincere apologies to you again. We, at EditGrid, will continue to serve our users with our best. </p> I\’m terribly sorry for your inconvenience. We think it is unacceptable as well. Believe me, we have worked non-stop to get that fixed in the past few hours. We\’ll also do all we can do to prevent this from happening in the future.

My colleague will explain what happened shortly afterward.

My sincere apologies to you again. We, at EditGrid, will continue to serve our users with our best.

]]> By: Justin http://blog.editgrid.com/archives/74#comment-1166 Justin Tue, 22 Aug 2006 17:06:11 +0000 http://blog.editgrid.com/archives/74#comment-1166 The recent dns downtime is unacceptable. The recent dns downtime is unacceptable.

]]>