Site (domain) outage update

[+Kyle Subscriber¹]

I found this from 2003 when i searched for Neowin Down - Neowin shut down

Wait what? 

 

That doesn't seem like Steve or Redmak. 

[LimeMaster]

Guys, another soution to get onto Neowin is to visit the old Neogamr domain: http://www.neogamr.net/forum/ (Most images even display correctly on that domain) :D

[ANON86364]

Guys, another soution to get onto Neowin is to visit the old Neogamr domain: http://www.neogamr.net/forum/ (Most images even display correctly on that domain) :D

Yeah I was about to suggest that. Logging in from the main page even works.

[DaveLegg Developer]

We've hopefully fixed the issue with images not loading correctly on neow.in, you may need to clear your caches to see it, but it should now be resolved.

[Andrew Lyle Global Moderator]

Hopefully it gets fixed soon :D

I can browse neow.in for awhile i suppose!

[LimeMaster]

Yeah I was about to suggest that. Logging in from the main page even works.

It's kind-of a pointless discovery now that images are working on the neow.in domain. :laugh:

[Haggis Veteran]

We've hopefully fixed the issue with images not loading correctly on neow.in, you may need to clear your caches to see it, but it should now be resolved.

 

 

seems to be all good :)

[KoL Veteran]

I found this from 2003 when i searched for Neowin Down - Neowin shut down

 

I remember that well, very glad to that 10+ years after that Neowin is still around and better than ever :)

I remember that.

 

 

We've hopefully fixed the issue with images not loading correctly on neow.in, you may need to clear your caches to see it, but it should now be resolved.

Yeah fixed here.

[Bertch]

We've hopefully fixed the issue with images not loading correctly on neow.in, you may need to clear your caches to see it, but it should now be resolved.

 

I don't use twitter and never knew about this domain until now, but I think I like it better and will stick with it even after the fix as long as no other issues pop-up.

[-T- Member]

Guys, another soution to get onto Neowin is to visit the old Neogamr domain: http://www.neogamr.net/forum/ (Most images even display correctly on that domain) :D

 

You're a genius, this is what got me the ability to log in. For some reason editing the hosts file didn't do it, and I cbf messing around with my other DNS settings

[+BudMan MVC]

Time for us to bombard ICANN with complaint letters.

 

For why - because neowin didn't follow the rules and use a valid email address that is monitored?  Yeah lets all jump on board ;)

 

If we should send complaints to anywhere it should be the registrar neowin is registered with "DOMAIN.COM, LLC"..  They should clearly have other contact info and such that they could of contacted their customer that whois info was not in compliance, etc.

Here is the thing, the info on domain needs to be current and monitored - even if hiding behind a 3rd party, they need to forward that on to correct contact info for the domain.

It sucks that neowin went down, but you can not blame ICANN on this.

[DaveLegg Developer]

They should clearly have other contact info and such that they could of contacted their customer that whois info was not in compliance, etc.

Indeed, the administrative and technical contacts were both up to date with email, phone and physical address, you'd think they would try those if the registrant email bounced.

[+BudMan MVC]

But here is the thing - I find it highly unlikely that ICANN replaced the ns info, that was your registrar, or the reseller not ICANN.

 

Now its possible someone reported you, or ICANN told the registrar to get it it updated.

 

you can report bad whois here

http://www.icann.org/en/resources/compliance/complaints/whois/inaccuracy-form

 

But as you can see from this statement on the site

The complaint is then forwarded to the sponsoring registrar, who must take reasonable steps to investigate and correct inaccurate data.

 

So if anyone has any issues with anyone it should be with your registrar and or reseller, shoot that domain that is pointed to for your NSes isn't even valid ;)

 

If me - I would change registrars ASAP..  I like namecheap, they have like a $4 xfer going currently I think..  Can't beat that with a stick!!

[Phouchg]

As much as I feel ICANN's a bunch of mindless jays, Bud's right on that one can't just yank the whole domain away like a rug. Some kind of correspondence had to happen. If it really did not, perhaps it's time to find somebody who cares even just slightly more.

[+BudMan MVC]

ICANN is not going to step in for something as trivial as whois info..  Its your registrar/reseller that dicked you over..  Its like the cable company shutting off your internet because they want to ask you a question because they are sure you will call ;)

 

I would drop who your currently using like a hot brick/patoato, faster than you can say Jack Robinson!!

[brink668]

Yay Neowin.net finally resolves again.  This was an important lesson anyway regarding the new Icann rules, I double checked all my stuff.

[+BudMan MVC]

^ can you point out the specifics where on what grounds registrar can take down your domain like that.. Seems you found them? I really have not been able to find where that is spelled out like what happened.

 

To me it was just the registrar/reseller being lazy about contacting someone that had not updated, etc.

[SnoopZ]

Yay Neowin.net finally resolves again.  This was an important lesson anyway regarding the new Icann rules, I double checked all my stuff.

Not for me yet.

[Steven P. Administrators]

^ can you point out the specifics where on what grounds registrar can take down your domain like that.. Seems you found them? I really have not been able to find where that is spelled out like what happened.

 

To me it was just the registrar/reseller being lazy about contacting someone that had not updated, etc.

We have the domain back.. this is what people are referring to http://community.discountasp.net/threads/new-icann-rule-could-lead-to-the-suspension-of-your-domain-name.21196/

 

Almost all of our domains were outdated, and I've updated them all.

 

Google DNS already resolves neowin.net for me.

[+Zlip792 MVC]

 

Google DNS already resolves neowin.net for me.

 

Now party time....

[brink668]

^ can you point out the specifics where on what grounds registrar can take down your domain like that.. Seems you found them? I really have not been able to find where that is spelled out like what happened.

 

To me it was just the registrar/reseller being lazy about contacting someone that had not updated, etc.

 

It is up to the Registrar, but ICANN put down some rules regarding domain contact verification.  The emails on file must work.

 

A compliant can filed by:

• From ICANN's website to the Registrar
• To REGISTRAR who owns the domain

The new complaint form, you can specify what is inaccurate or not accurate, it is then up to the Registrar to contact that person or company.  I believe the only method they are required to do so is by email.  One of my friends had an email address that no longer worked similar to Neowin.net's issue and when he logged into the Registrar it says "10 days" has passed since we first contacted you regarding the incident.  As soon as we updated the email address he received a verification email within about 10minutes and when he clicked it the link within the email for confirm, the Registrar automatically removed the notice on the account and the WHOIS field updated to: Active/Accurate.  

 

To me if that email address is getting bounce backs or if you change the contact information you will be notified and asked to update.  No one called the phone listed on the Whois which was correct and up to date, so the email is the most vital part.

 

GoDaddy seems to between 15-30days until they will suspend the domain if no verification takes place.  I have seen other users say it may take 30-60days if not verification is met.

 

Another source,

https://iwantmyname.com/blog/2014/01/icanns-new-rules-for-domain-registrants-require-you-to-verify-your-contact-details.html

[Steven P. Administrators]

It came from ICANN. I've been told that although the domain has been restored, the registrar is still required to contact ICANN with an update on this particular incident. Knowing that it was the primary contact email address that was the issue, and now isn't, we shouldn't expect further action from ICANN because we acted on their issue.

 

In summary, ICANN contacted our registrar with the WHOIS violation and demanded it be suspended, and also offered a solution to the problem. I don't know if we were reported because that information wasn't forthcoming. 

[Steven P. Administrators]

PS: We had domian privacy and namesafe enabled on neowin.net so even the registrar can't update the email address for us, it's not really their job to modify domains without the customer knowing.

[+BudMan MVC]

"In summary, ICANN contacted our registrar with the WHOIS violation and demanded it be suspended"

 

This is what I question -- who told you this your registrar/reseller?  I know the rules on what needs to be working, etc.  But have never seen ICANN make a demand.. Which is the info I was looking for in a change to the rules..  Does someone have a link to where ICANN in words says they will demand suspension or take down on such a violation.  This is what I can not find.

[Steven P. Administrators]

 

Dear Registrar, Domain.com, LLC - 886: 

 

ICANN received the Whois inaccuracy report below. It claims that the contact information associated with the domain name is inaccurate: 

 

neowin.net 

 

As required under Section 3.7.8 of the Registrar Accreditation Agreement (RAA), please take reasonable steps to investigate this Whois inaccuracy claim; and, where appropriate, correct the contact information, suspend or delete the domain registration. 

 

To determine whether your registrar is in compliance with Section 3.7.8 of the RAA, please indicate in the email reply which option below describes the actions taken by your registrar on or before 18 February 2014: 

 

1. Your registrar confirmed that the reported inaccuracy was corrected. 

 

2. Your registrar obtained satisfactory verification from the registrant that the data was correct. 

 

3. Your registrar suspended, deleted, cancelled or otherwise deactivated the domain name. 

 

4. Your registrar did not investigate the inaccuracy as Section 3.7.8 requires. 

 

If 1 or 2 above applies, please provide copies of your registrar's correspondence with the registrant while investigating this Whois inaccuracy claim (including dates and times and means of inquiries, telephone number, e-mail addresses, and postal addresses used) in accordance with Section 3.4 of the RAA. 

 

Please send the records requested above via reply email (no more than 4 MB total) by 18 February 2014 and do not change the email subject heading. Please provide records in .TXT, .PDF, or .DOC(X) format. 

 

Thank you in advance for your cooperation. 

 

Sincerely, 

 

Yungsheng Wang 

ICANN Contractual Compliance 

 

############################################ 

 

The problem summary: 

 

Domain being reported: neowin.net 

 

Time of submission/processing: Mon Jan 27 01:01:30 2014 

 

Problem in whois block: Technical Contact 

--- Error in email: Incorrect email 

--- Comment: E-mail address doesn't work. This bounces back: 

 

Your message to <[email protected]> was automatically rejected: 

Quota exceeded (mailbox for user is full) 

 

Problem in whois block: Administrative Contact 

--- Error in email: Incorrect email 

--- Comment: E-mail address doesn't work. This bounces back: 

 

Your message to <[email protected]> was automatically rejected: 

Quota exceeded (mailbox for user is full)