Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We got 4 ips on our server, and I noticed that one of our IP's appears to be blocked by a big whois providor.

Is there a way I can route whois lookups over a different IP - not just eth0?

share|improve this question
up vote 2 down vote accepted
 route add <ip of whois server>/32 <preferred interface> 

should do it

share|improve this answer
No mention of OS, so the Windows equivalent is: route add <ip of whois server> mask <ip address of preferred interface> – Mark Henderson Apr 17 '10 at 1:47
If there's not multiple gateways or a router handling source NATs, would specifying the alias interface be enough? – Warner Apr 17 '10 at 1:49
Well, the question did mention eth0, so I took a stab – Matt Simmons Apr 17 '10 at 1:49
Sorry, didn't answer your question. If the remote server is blocking some (but not all) of your IPs, you can use route to prefer the interface with the unblocked IP. – Matt Simmons Apr 17 '10 at 2:02
That works great! – Wizzard Apr 17 '10 at 2:33

You'll need to alter your DNS settings to another IP address you own and alter your web server configurations to reflect the changes.

share|improve this answer
He's asking how to change the source IP when routing out of the system with a client. – Warner Apr 17 '10 at 1:36
Damnit, I wasn't sure if he was asking that or what. I was going to post the route answer as well, but I read into that DNS was the issue. – David Rickman Apr 17 '10 at 3:31

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.