[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-users] RE: Speed Issue and a funny one... (continued)
- Subject: [cobalt-users] RE: Speed Issue and a funny one... (continued)
- From: "Nicolae" <nicolaep@xxxxxxxxxxxxxxxxxx>
- Date: Sat Feb 23 03:27:01 2002
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
Message: 10
Date: Fri, 22 Feb 2002 13:13:59 -0800
From: Jeff Lasman <jblists@xxxxxxxxxxxxx>
Organization: nobaloney.net
To: cobalt-users@xxxxxxxxxxxxxxx
Subject: Re: [cobalt-users] RE: No.. No... Not hosting on cable...
Reply-To: cobalt-users@xxxxxxxxxxxxxxx
// as long as I get what I am paying for is fine.
Although my buddy pays the same with his own server with
VitalStreams and he gets lllllllloooooooooooots more...
http://www.vitalstream.com/
My thought about serverrack.net was that they ran fiber
but not yet. They have T1 lines. So I guess that is a
typical speed line for the $150/month.
Don't ask why but VitalStream is 15 minutes from my house
and ServerRack.net is days from my house if I was to drive.
I've had InternetSeer give me some warning on some domain
I had monitored for free but like you said, pinging it
24/7 or whatever dslreports or InternetSeer do might not
be as accurate.
You gots' to spend some to learn some... What better way
to do that than this way.
I posted this in the past elsewhere and I thought it
was funny in a stupid way... cuz I had no clue what I was
doing or did. Last time I used UNIX was 4 or so years
ago SCO UNIX 2.x which was limited.
Check this out:
[quote]
Cobalt Settings
Control Panel --> Network
General Settings
Host Name: enigma-networks
Domain Name: enigmabiz.com
Primary DNS: 65.170.79.2
Second DNS: 65.170.79.3
Default Gateway: 65.170.79.1
Interface Settings:
IP Address: 65.170.79.187
SubNet Mask: 255.255.255.0
Under Site Management I have:
As a Virtual Site:
enigma-networks.enigmabiz.com 65.170.79.187
I read an article on Interliant.com and added the following to
above Site Management:
ns1.enigmabiz.com 65.170.79.2
ns2.enigmabiz.com 65.170.79.3
Now I am not sure if I did that correct but I did follow step by step.
[/quote end]
I really should not post this here if you understand what happened
by me adding the ns1. and ns2. That tells you I had
no clue about DNS :). Thanks to D. Lucas here
I don't use DNS, and i changed host name to 'www' easier,
I still don't use my 2nd IP or the entire Raq...
Ou, and I also returned the O-Reilley DNS & Bind book back
because didn't help much on the Cobalt Raq.
What does a used / refurbished Cobalt Raq 4 go for these days?
Thanks,
--
EnigmaBiz.Com
> No... No.. mis-communication here. I am not looking to host on cable
> or ever, but thought about it. I am at home PC running Time Warner
> cable connection to browse the internet.
--We're all glad you decided against it <smile>.
> I use a data-center
> in Virnginia (I am in Calif) and have a leased Cobalt 4 Raq
> unit in their data center.
--How come so far from home, lots of people offer lots of good stuff in
--California, you know. We host at Inflow in San Diego.
> http://www.dslreports.com/monitored/pp/65.170.79.187
> I think the reports I get above from DSLReports might be able
> to tell my ISP that something is wrong and their new T1 Line
> they got in the datacenter is not really helping...
--It's just a chart showing the result of a lot of pings. I don't know
--how often they're pinging, but if they're doing it continuously you
--should know that enough pings can definitely slow down a server.
--What kind of connectivity does your datacenter have? You still haven't
--told us who you're with, I don't think, but their T-1s are supplied by
--Sprint.
--When I use Visualware's VisualRoute Server from Dulles, Virginia, to
--trace to them in in Manassas, Virginia, the traceroute goes from Dulles,
--to Dallas, to Ft. Worth (both Texas), then to Atlanta, Georgia, then to
--Elkridge, Maryland, then back to Virginia. Kind of bounces all over the
--place. That's what can happen when one company (Sprint in this case)
--tries to keep the data on its own Network.
--Now while the traceroute may be wrong in that some IP#s may not be where
--Arin thinks they are, nevertheless, that's a lot of hops from Dulles to
--Manassas.
> I am only hosting sites for cleints I design their site for.
> I might as well lease a cobalt for 150/month and host 15-20
> sites pay the bill and also park my 10 or so domains also.
--Sounds good, but you do get what you pay for. We charge more; in fact
--probably what you'd consider a lot more, but we offer more as well. For
--starters, 100 gigabytes of transfer per month, and bandwidth shaped at
--each machine to the equivalent of 3-1/3 T-1 lines.
> Maybe smeone can shed a light on this report:
> http://www.dslreports.com/monitored/pp/65.170.79.187
> Let me know what you think... you can email me
> or reply here...
--It's a graphic representation of a whole bunch of pings. The numbers
--represent round-trip times between them and your machine. Often called
--"latency". It's not really indicative of the speed between your server
--and anywhere else; for example, if you pinged anyone through a satellite
--connection your latency would be in the area of 150 to 300 or more, but
--your speed would still be pretty fast.