[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-users] reaching an additional IP#
- Subject: [cobalt-users] reaching an additional IP#
- From: Jeff Lasman <jblists@xxxxxxxxxxxxx>
- Date: Tue Feb 29 15:58:31 2000
Does anyone know any reason why a RaQ3 should not react to a ping on an IP#
if the IP# is set up for a domain.
The problem is that our first IP#, ending in .98, is pingable.
Our second, ending in .99, isn't. Even when we've set up a domain on the
RaQ3 using that IP#.
I've found this line in /var/log/messages:
> Feb 28 08:45:08 www named[9590]: listening on [xxx.xxx.xxx.99].53 (eth0:0)
which indicates to me that the RaQ3 IS listening on that IP#.
But no browser can find any of the sites there by IP#, and no nameserver
can find the nameserver at that IP#.
I've found nowhere in the gui web-based interface to add additional IP#s,
except when setting up sites.
Under Server Management, Network, the gui is set for IP Address
xxx.xxx.xxx.98 and the subnet mask is set for 255.255.255.0. I can't find
anywhere else to change or add anything.
On my RaQ2, I don't have to do anything to enable listening on that
IP#. Is there anything else that has to be done on a RaQ3 besides putting
up a website at an IP#, to get it to accept packets at that IP#?
Thanks.
Jeff
--
Jeff Lasman <jblists@xxxxxxxxxxxxx>