Domains on aliased IPs are not resolving.


First off, been a proud user of the panel for over a year now, and loving every minute of it.

Now, my question: I set up a new server earlier this year with IW on it, and it’s been running smoothly ever since. The server has 1 primary IP and 4 secondary IPs that are aliased on the same adapter. This configuration was working fine, but sometime in the past 2 weeks, it’s stopped working and all domains on the aliased IPs have stopped resolving. All domains on the primary IP work just fine. I’ve been up and down this box and all kinds of configuration files trying to figure out what could be causing this, but I’ve yet to find why this is happening. As near as I can tell, the configuration has not changed from before this occurred.

Any ideas as to what could cause this, and, of course, what I can do to fix it?


Hi Dave,

Are the aliased IPs pingable? There’s no correlation between IPs that are aliased and the DNS system, so I’m not sure what to make of that - if what you mean by resolving is in fact related to DNS. Maybe a couple examples of working/not working domains would help us help you.


I didn’t even think to check that, but no, they are not pingable. And as I said in my original post, I’ve not changed any configuration inside or outside of Nodeworx since the server was setup. The only thing that’s been done inside the system is setting up new accounts.

Working domain:
Non-working domain:

Both are on the same server, but are assigned to different IPs in Nodeworx. In addition, the working domains are all on the primary IP (as I said in my first post), but I’ve just noticed today that one of those is non-working now as well (

All the IPs are listed in Nodeworx as active on the system and in Nodeworx, and they are showing the correct aliased device as well. If I SSH into the box and check the interface status using ifconfig, they all show correctly and are listed as up and running as well.

Any ideas?


That’s odd Dave. If I were you’d I’d ask your datacenter folks (or whoever manages the network) to get involved and see if they can tell why the IP responding despite apparently being configured correctly on your server. If those IPs are somehow misconfigured on your box they should be able to point to the problem, and if it’s a routing issue, they’ll have to take care of it as well. I’d give them a list of all the IPs that aren’t responding, your server login info, and have them investigate.


Thanks for the info Paul, I’ll get in touch with them ASAP. I was just trying to rule out software/configuration issues first before I had to involve a third party.

Thanks again.