Results 1 to 3 of 3
Hi,
My nslookup shows an entry for 60.60.60.1. But, I have added a route entry 60.60.60.1 to go out of interface eth1. so, from the linux server if I ping ...
- 03-02-2010 #1Just Joined!
- Join Date
- Mar 2010
- Posts
- 1
nslookup
Hi,
My nslookup shows an entry for 60.60.60.1. But, I have added a route entry 60.60.60.1 to go out of interface eth1. so, from the linux server if I ping 60.60.60.1, it is going out of eth0 instead of eth1. Does someone know what is the reason ?
Is it that eth0 has more preference than eth1 that though we force the packets to go out the interface eth1.
Thanks,
- 03-03-2010 #2
If you don't have a route set then anything that isn't known will be sent out the default gateway. Not sure I understand what you mean with 'My nslookup shows an entry for 60.60.60.1'. Could you post the output of nslookup so that we can see what you are talking about? It could be that in resolv.conf you have that DNS server set.
- 03-04-2010 #3Just Joined!
- Join Date
- Jul 2009
- Posts
- 4
You know, this actually sounds like a routing problem or question, as long as we remove the first sentence. It could be a box with two ifaces on the same net, perhaps both of them on the 60.60.60.x . If so, it may explain why there's a seeming preference for eth0 over eth1 for outgoing traffic, since often routing is done internally.
I'd expect a host route to definitely choose the iface mentioned, but I'd want to see a route table as well as that resolv.conf (and nslookup output) just for kicks.


Reply With Quote