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

[dkindlund]

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

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonra...@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-ta...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.

[Frederick Cheung]

On Apr 20, 4:57 pm, dkindlund <dkindl...@gmail.com> wrote:
> 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

[dan]

is there a direct ip for ruby rails site?

[jhaagmans]

You can use rubyonrails.com now.

[Moo]

API doesn't work with .com

[Philip Hallstrom]

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

http://railsapi.com/

> To post to this group, send email to rubyonrails-
> ta...@googlegroups.com.

> To unsubscribe from this group, send email to rubyonrails-ta...@googlegroups.com
> .

[Frederick Cheung]

On Apr 21, 12:28 am, Philip Hallstrom <phi...@pjkh.com> wrote:
> Go here and download whatever set of rdocs you need... then you don't  
> have to worry about the official site anymore :)
>

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

[Rick]

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

On Apr 21, 2:13 am, Frederick Cheung <frederick.che...@gmail.com>
wrote:

[Amala Singh]

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?

--
--
Nandri(Thanks in Tamil),
Amala Singh

[Peter De Berdt]

On 21 Apr 2010, at 14:56, Amala Singh wrote:

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?

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

[Amala Singh]

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.

--
--
Nandri(Thanks in Tamil),
Amala Singh

[Moo]

> 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.

On Apr 21, 7:39 am, Amala Singh <amalasi...@gmail.com> wrote:
> 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.
>

> On 21 April 2010 15:26, Peter De Berdt <peter.de.be...@pandora.be> wrote:
>
>
>
>
>
> > On 21 Apr 2010, at 14:56, Amala Singh wrote:
>
> > 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?
>
> > 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
>
> >  --
> > You received this message because you are subscribed to the Google Groups
> > "Ruby on Rails: Talk" group.
> > To post to this group, send email to rubyonra...@googlegroups.com.
> > To unsubscribe from this group, send email to

> > rubyonrails-ta...@googlegroups.com<rubyonrails-talk%2Bunsu...@googlegroups.com>
> > .

[Shiv Narayan Gautam]

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 :)

[Amala Singh]

Good news. Thank you.

[tonypm]

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

[Fernando Perez]

> 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.
--
Posted via http://www.ruby-forum.com/.

[Marnen Laibow-Koser]

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,
-- 
Marnen Laibow-Koser
http://www.marnen.org
mar...@marnen.org

[steve ross]

On Apr 22, 2010, at 5:35 AM, Marnen Laibow-Koser wrote:
>
> 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,

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?

[Marnen Laibow-Koser]

Steve Ross wrote:
> On Apr 22, 2010, at 5:35 AM, Marnen Laibow-Koser 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. :D

Best,
--
Marnen Laibow-Koser
http://www.marnen.org
mar...@marnen.org
--
Posted via http://www.ruby-forum.com/.

[Fernando Perez]

> 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!

--
Posted via http://www.ruby-forum.com/.