Jump to content

Recommended Posts

Last I heard (last week) it was still tango uniform. Given the extended time it's been down, I have to suspect there's something more to the story than what we're hearing. A simple hack could have been fixed long before now.

Link to post
Share on other sites

The last thing on LSP I saw today about it was.....

The story is on Facebook. Short version - large amount of spam - lack of help from GoDaddy - waylaid emails, "ownership" questions, lack of dedicated IT people who routinely monitor the forum.

Currently and actively being resolved by volunteer forum members to make a better end product.

:cheers:

Jerry

Link to post
Share on other sites

Last I heard (last week) it was still tango uniform. Given the extended time it's been down, I have to suspect there's something more to the story than what we're hearing. A simple hack could have been fixed long before now.

It was never hacked, Go Daddy noticed the site was registered in a name of a person who is no longer a member there. They shut it down until the ownership was transferred. Sounds like that isn't going smooth.

Link to post
Share on other sites

It was never hacked, Go Daddy noticed the site was registered in a name of a person who is no longer a member there. They shut it down until the ownership was transferred. Sounds like that isn't going smooth.

How would GoDaddy know, and why would that be relevant to them?

I could believe, however, that somebody other than to owner tried to gain control of the domain.

Link to post
Share on other sites

How would GoDaddy know, and why would that be relevant to them?

Because in this age of litigation, GoDaddy might want valid contact information and ownership of the site in case somebody did something on the site that resulted in a law suit against GoDaddy. Every host like GoDaddy has rules that they expect people to follow to keep traffic and revenue alive and possible legal issues minimized.

Deke

Link to post
Share on other sites

The actual reason why Z5 was taken down:

(...) Your zone-five.net hosting account caused a significant overload of shared resources CPU & Memory for the server on which it resides.

This overload threatened the health of the server and, in turn, the connectivity of other websites housed on it.

We understand that this situation was not intentional. However, due to the significant negative impact on the shared hosting environment and it's availability to other customers,

it became necessary for our hosting administrators to disable website access on your hosting space. (...)

Pretty much hosting industry common practise. It's not "a GoDaddy thing".

Domain name contact details - obligations:

Obligations of the registrant (owner of a domain name)

When you register a domain name, you must give your registrar accurate and reliable contact details and correct and update them promptly if there are any changes during the term of the registration period. This obligation is part of your registration agreement with the registrar (GoDaddy). If you give wrong information on purpose, or don't update your information promptly if there is a change, your domain name registration may be suspended or even cancelled. This could also happen if you don't respond to inquiries by your registrar if they contact you about the accuracy of your contact information.

Just to put it straight, Z5 was not taken down due to "domain ownership issues".

However, due to obsolete email contact details they failed to respond to GoDaddy's requests in time. In the meantime, they fixed this issue by updating the contact details.

GoDaddy's interest in valid/reliable domain name contact details:

The obligation to provide valid and reliable contact data (which can be retrieved via a WHOIS query) rests first and foremost with the registrant (owner of a domain name).

Any ICANN-accredited registrar (GoDaddy/Enom/Tucows, etc.) has the obligation to advise customers of their duty to provide valid/reliable data. By signing/reading the registrar agreement, the owner of a domain name acknowledges such policy accordingly. In turn, ICANN-accredited registrars are dutybound (WDRP) to annually submit current WHOIS data to the owner of a domain name in order to review and, if necessary, to update the contact details. Vis-à-vis ICANN, acting as parent body, registrars have to present documentation that they positively complied with the so-called WHOIS Data Reminder Policy (WDRP).

In case of domain name related issues, the owner of the domain carries the liability. If the owner fails to respond, the complainant may approach the "registrar" (e.g. GoDaddy) making his complaint, and in case the complaint may be eligible (e.g. court order), the registrar will take appropriate action.

GoDaddy support:

They provide the domain name registration, the tools to administer a domain name and the webspace/hosting.

It's by no means their job to fix issues that are related to third party software. They contacted the account and domain owner in order to inform the operators, to request appropriate action to be taken

and to fix those issues ASAP. In addition, they also provided to the point information on how to fix such issues. But that's exactly where GoDaddy's responsability ends.

Z5:

They've got to remove the spam accounts and implement appropriate tools to even prevent spambots/human spammers from registering.

For the sake of fairness, if you're not a dedicated IT guy or hand in glove with forum software adminstration, this may be quite a challenge.

Once this will have been accomplished, GoDaddy may turn the power switch on again.

Erik

Edited by Airfixer
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...