api.rubyonrails.org site is taken over by a domain squatter

rubyonrails-talk
1

All,

Visiting http://api.rubyonrails.org now redirects to an domain squatter page.

If you're not seeing it (probably because the original site may still be cached by an upstream proxy), look at CorelCDN's cached version of the page:

http://api.rubyonrails.org.nyud.net/

$ nslookup rubyonrails.org Non-authoritative answer: Name: rubyonrails.org Address: 64.74.223.46

$ nslookup api.rubyonrails.org Non-authoritative answer: Name: api.rubyonrails.org Address: 64.74.223.46

Looks like either the legit website got owned and is now serving up bad content, or the domain squatter was kind enough to replicate the rubyonrails.org front page.

$ dig -x 64.74.223.46

; <<>> DiG 9.4.2-P2.1 <<>> -x 64.74.223.46 ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 15105 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION: ;46.223.74.64.in-addr.arpa. IN PTR

;; AUTHORITY SECTION: 223.74.64.in-addr.arpa. 10800 IN SOA ns-a.pnap.net. hostmaster.pnap.net. 2008060200 28800 1800 604800 43200

2

All,

Visitinghttp://api.rubyonrails.orgnow redirects to an domain squatter page.

If you're not seeing it (probably because the original site may still be cached by an upstream proxy), look at CorelCDN's cached version of the page:

This seems to happen pretty much every year - the autorenew for the domain fucks up the domain (see http://twitter.com/dhh and http://groups.google.com/group/rubyonrails-core/browse_thread/thread/2b2b64922e7f731c#)

Fred

3

is there a direct ip for ruby rails site?

4

You can use rubyonrails.com now.

5

API doesn't work with .com

6

Go here and download whatever set of rdocs you need... then you don't have to worry about the official site anymore :slight_smile:

http://railsapi.com/

7

Go here and download whatever set of rdocs you need... then you don't
have to worry about the official site anymore :slight_smile:

or generate the docs locally (rake doc:rails) like that you don't have to worry about having an internet connection

8

Any idea on how long it takes to recover from this annual screw-up? Eyecandy and grublinks are no substitute for a productive community site.

Rick

9

This is a sign of ROR losing credibility. It is such a shame that it has happened to a wonderful innovation. Why they are going for RoR3 and so on, if they cannot maintain the existing things better?

10

What a pointless remark. 37signals paid the renewal of the domain well beforehand, their registrar screwed up again. That’s hardly their fault and has nothing to do with 37signal’s infrastructure. It’s not the first major site to have this problem btw, can happen to everyone.

Best regards

Peter De Berdt

11

Pointless remark? Ha. Cant this be avoided for the second time if not for the first time? I dont still believe this it could happen to ROR.

12

Pointless remark? Ha. Cant this be avoided for the second time if not for the first time? I dont still believe this it could happen to ROR.

it's not the freaking rails framework man. it's the domain name registrar.

13

DHH just tweeted saying that the domain is back up. Waiting for all the DNS servers to cache it. And the domain is registered for 10 years. So there you go Amala. Happy now :slight_smile:

14

Good news. Thank you.

15

Thanks - it may have only been a short time, but I was missing the guides.

16

What a pointless remark. 37signals paid the renewal of the domain well beforehand, their registrar screwed up again. That's hardly their fault and has nothing to do with 37signal's infrastructure.

It's 37signals' fault as it already happened in the past and they did not take action to prevent it from happening again.

See you next year.

17

Fernando Perez wrote:

What a pointless remark. 37signals paid the renewal of the domain well beforehand, their registrar screwed up again. That's hardly their fault and has nothing to do with 37signal's infrastructure.

It's 37signals' fault as it already happened in the past and they did not take action to prevent it from happening again.

See you next year.

My thoughts exactly.

Best,

18

In case you missed DHH's announcement, the domain has been renewed through 2020. Unless there is some seriously flaky bookkeeping going on with the domain registrar, the issue should not come up next year.

Enough?

19

Steve Ross wrote:

My thoughts exactly.

Best,

In case you missed DHH's announcement, the domain has been renewed through 2020. Unless there is some seriously flaky bookkeeping going on with the domain registrar, the issue should not come up next year.

We can hope.

Enough?

I guess we'll know next April. :smiley:

Best,

20

In case you missed DHH's announcement, the domain has been renewed through 2020. Unless there is some seriously flaky bookkeeping going on with the domain registrar, the issue should not come up next year.

Enough?

Imagine what would happen if he was in charge of maintaining tweeter.com DNS!