Midwest Nano community now open!
Oct. 12th, 2005 03:10 am![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png)
In the interest in finding contacts a little closer to home, I created
![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-community.gif)
Hope to see you soon.
Regards,
~TS
We need your help!
Posted by Chris Baty on 2005/10/12 18:40:42 (342 reads)
Hey there! We are sad to report that Earthlink, one of the US's largest ISPs, is allowing an internal problem to persist that makes the NaNoWriMo.org site inaccessible to their customers. We've contacted them about this repeatedly with no success. And we would love your help in getting the issue resolved. Russ has put together an overview of the issue, which I've pasted below. Please, if you have a moment today, contact Earthlink andask them in the kindest way possible to devote a smidge of their mighty resources towards fixing the problem. Together, we'll get it taken care of!
(from Russ)
Here's the problem: Earthlink's DNS servers are returning an incorrect NS record for www.nanowrimo.org.
They have been doing this since September 14th.
The problem seems to have been fixed once or twice, only to break again. Sometimes the incorrect record is always returned, sometimes Earthlink alternates between correct and incorrect information.
The result of this is that most of the time Earthlink subscribers cannot access the NaNoWriMo website.
This problem extends to subscribers of other Earthlink companies like PeoplePC and MindSpring.
Many Wrimos have spent many hours of their time with Earthlink Tech Support trying to get them to fix this problem. In some cases, Earthlink staff have agreed that there is a problem, and have promised to have Earthlink technicians fix it. In some cases, Earthlink staff have blamed the victim, telling them their computer was at fault. In some cases, Earthlink staff have blamed NaNoWriMo, claiming that we are purposefully blocking Earthlink subscribers from our site (which
we couldn't do even if we wanted to).
In no cases has Earthlink actually fixed the problem.
We're asking you, the general NaNoWriMo community, to give your Earthlink-bound brethren a hand by asking Earthlink - politely! - to fix this problem.
Here are some Earthlink tech support email addresses that you can try:
hostmaster@earthlink.net
webmaster@earthlink.net
abuse@earthlink.net
epasupport@earthlink.net
You can also try to email, live chat, and phone links on this page:
http://support.earthlink.net/
In order to support your case, you should include the following technical information in your communication:
Here are the correct nameservers for nanowrimo.org:
% dig ns nanowrimo.org
nanowrimo.org. 2250 IN NS ns1.quickserve.com.
nanowrimo.org. 2250 IN NS ns0000.ns0.com.
Here are the incorrect nameservers that Earthlink is returning:
% dig ns nanowrimo.org @ns3.earthlink.net
nanowrimo.org. 3047 IN NS PARK10.SECURESERVER.NET.
nanowrimo.org. 3047 IN NS PARK9.SECURESERVER.NET.
We've checked all of the root servers for the .org TLD and none of them are wrong.
Finally, if you know someone who is having this problem, please ask them to email help@nanowrimo.org. We'll send them instructions to a
workaround for this issue.
Thank you!
We need your help!
Posted by Chris Baty on 2005/10/12 18:40:42 (342 reads)
Hey there! We are sad to report that Earthlink, one of the US's largest ISPs, is allowing an internal problem to persist that makes the NaNoWriMo.org site inaccessible to their customers. We've contacted them about this repeatedly with no success. And we would love your help in getting the issue resolved. Russ has put together an overview of the issue, which I've pasted below. Please, if you have a moment today, contact Earthlink andask them in the kindest way possible to devote a smidge of their mighty resources towards fixing the problem. Together, we'll get it taken care of!
(from Russ)
Here's the problem: Earthlink's DNS servers are returning an incorrect NS record for www.nanowrimo.org.
They have been doing this since September 14th.
The problem seems to have been fixed once or twice, only to break again. Sometimes the incorrect record is always returned, sometimes Earthlink alternates between correct and incorrect information.
The result of this is that most of the time Earthlink subscribers cannot access the NaNoWriMo website.
This problem extends to subscribers of other Earthlink companies like PeoplePC and MindSpring.
Many Wrimos have spent many hours of their time with Earthlink Tech Support trying to get them to fix this problem. In some cases, Earthlink staff have agreed that there is a problem, and have promised to have Earthlink technicians fix it. In some cases, Earthlink staff have blamed the victim, telling them their computer was at fault. In some cases, Earthlink staff have blamed NaNoWriMo, claiming that we are purposefully blocking Earthlink subscribers from our site (which
we couldn't do even if we wanted to).
In no cases has Earthlink actually fixed the problem.
We're asking you, the general NaNoWriMo community, to give your Earthlink-bound brethren a hand by asking Earthlink - politely! - to fix this problem.
Here are some Earthlink tech support email addresses that you can try:
hostmaster@earthlink.net
webmaster@earthlink.net
abuse@earthlink.net
epasupport@earthlink.net
You can also try to email, live chat, and phone links on this page:
http://support.earthlink.net/
In order to support your case, you should include the following technical information in your communication:
Here are the correct nameservers for nanowrimo.org:
% dig ns nanowrimo.org
nanowrimo.org. 2250 IN NS ns1.quickserve.com.
nanowrimo.org. 2250 IN NS ns0000.ns0.com.
Here are the incorrect nameservers that Earthlink is returning:
% dig ns nanowrimo.org @ns3.earthlink.net
nanowrimo.org. 3047 IN NS PARK10.SECURESERVER.NET.
nanowrimo.org. 3047 IN NS PARK9.SECURESERVER.NET.
We've checked all of the root servers for the .org TLD and none of them are wrong.
Finally, if you know someone who is having this problem, please ask them to email help@nanowrimo.org. We'll send them instructions to a
workaround for this issue.
Thank you!