[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Apache not responding
- Subject: Re: [cobalt-users] Apache not responding
- From: Jeff Lasman <jblists@xxxxxxxxxxxxx>
- Date: Fri Jan 19 16:17:18 2001
- Organization: nobaloney.net
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
Jens Kristian Søgaard wrote:
> > This confuses me. You can't ping a site. You can ping an IP address.
> > Is that what you mean?
>
> You can ping a site in the sense that you can ping the name. The ping client
> can ofcourse resolve names. You're just being a hairsplitter now.
Yes and no. You can ping a URL that consists of merely a
hostname.domainname combination, and if you do, you can say you're
pinging a site, but in fact you're still pinging the IP# the
hostname.domainname resolves to. If if your DNS or your hosts file is
wrong, that could be the problem. That's why I made the comment I did.
> > > I can't telnet to port 80,25,110, no servers
> > > (cucipop, senmail, apache) are listening.
>
> > You are using "dots" and not "commas", right? And you do know that
> > 80.25.110 is NOT a complete IP#, right?
>
> Ehm, he's talking about _ports_, and not _ip's_. So he's completely right
> about that notation.
Sorry, must have been half asleep when I wrote that. Mea culpa. I
apologize.
Jeff
--
Jeff Lasman <jblists@xxxxxxxxxxxxx>
nobaloney.net
P. O. Box 52672
Riverside, CA 92517
voice: (909) 787-8589 * fax: (909) 782-0205