Stefan, His server is probably sending to you via the default route which is his primary IP. A netstat -nr output would be nice... See man page for route command for options to add a route using a specific interface. I think it would be: route add -host <your host> -gw <his existing gw IP address> eth0:0
or some variation of this... in the command, <your host> is the name or IP of your server, <his existing gw IP address> is the IP of his gateway. not sure of the syntax, your mileage may vary... HTH Rick -----Original Message----- From: Stefan Neufeind [mailto:[EMAIL PROTECTED] Sent: Thursday, February 27, 2003 11:25 AM To: [EMAIL PROTECTED] Subject: DNS: Binding to eth0:0-ip but why using eth0-ip for outgoing traffic? Hi, I'm running a separate bind-daemon as secondary-dns on some server of a friend. He assigned me an IP (eth0:0) which I can use to bind my own DNS-instance to. But when it comes to zone-transfers the secondary-DNS still connects to my primary-DNS using the "official" eth0 ... which, if you take it correct, is not the IP of my DNS- instance. Am I just too dumb or how to work around this IP-problem? Thank you very much Stefan -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
