Web Hosting Talk : Web Hosting Main Forums : Hosting Security and Technology : Only one of my ip's are working... What can I do?

[CrewXp]

I've had this problem before, sent my datacenter an email about it, and it was fixed. But the server was just down for a while recently and now only one ip (the main ip) is working. What can I do to get the other ip's working again? I've tried restarting the server the fixrdnc scripts. Nothing working so far. A lot of sites I have run off of the other ip's though.

Thx alot.

[GFuse|Kevin]

What is the output of ifconfig -a

[CrewXp]

eth0 Link encap:Ethernet HWaddr 00:50:70:C4:2E:11
inet addr:66.197.204.245 Bcast:66.197.204.255 Mask:255.255.255.240
inet6 addr: fe80::250:70ff:fec4:2e11/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:214382 errors:0 dropped:0 overruns:0 frame:0
TX packets:315479 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:15842522 (15.1 MiB) TX bytes:436805194 (416.5 MiB)
Interrupt:11 Base address:0x6000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:12149 errors:0 dropped:0 overruns:0 frame:0
TX packets:12149 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4083286 (3.8 MiB) TX bytes:4083286 (3.8 MiB)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

in whm, just fyi, it says all of them are there too. I've used them before, no problem..

66.197.204.245
66.197.204.246 Remove
66.197.204.247 Remove
66.197.204.248 Remove
66.197.204.249 Remove

[CrewXp]

okay. this is fixed now. for anyone who has this problem in the future:

It appears that the command "/etc/rc.d/init.d/ipaliases restart" was not present in the rc.local control file. I have added it. It works now. Thx

[GFuse|Kevin]

If they are not listed in ifconfig -a then they are not tied to the NIC.

ifconfig eth0 inet 66.197.204.246 netmask 255.255.255.240 -alias
ifconfig eth0 inet 66.197.204.247 netmask 255.255.255.240 -alias
ifconfig eth0 inet 66.197.204.248 netmask 255.255.255.240 -alias
ifconfig eth0 inet 66.197.204.249 netmask 255.255.255.240 -alias

Then they sould be listed via ifconfig -a and pingable (depending on iptables rules).