bind in multi eth (virtual) situations

Angel Luis Uruñuela angel at nominalia.com
Thu Sep 21 07:42:08 UTC 2000


Angel Luis Uruñuela wrote:
> 
> amh wrote:
> >
> > i've read and read and searched and searched, but can't find the info i'm
> > looking for.
> >
> > i'll give a rough example.
> >
> > i have a machine with several ips tied to it (linux, 2.2.16) as eth0 thru
> > eth0:whatever.
> >
> > my nameserver address is *not* the default (eth0) address of the machine.
> >
> > i use listen-on to force it to listen to the nameserver ip, but i want all
> > communication with bind to be done via this ip.
> >
> > i can't find any directive to force *all* communication to be via this
> > 'virtual' ip. a good example is NOTIFYs sent by this primary server, they're
> > always seen by the secondarys as coming from the primary's default ip, *not*
> > the nameserver ip.
> >
> 
>         You can't do this with any directive. You must use the routing table.
> For example:
> 
> /sbin/route del -net default dev eth0
> /sbin/route del -net 172.24.64.0 netmask 255.255.255.0 dev eth0
> /sbin/route add -host <ROUTER_IP> dev eth0:1
> /sbin/route add default gw <ROUTER_IP> dev eth1:0
> 
> Regards,

	And /sbin/route/ add net 172.24.64.0 netmask 255.255.255.0 dev eth0:1
;-)
> 
> --
> Angel Luis Uruñuela <> Unix Systems Administrator
> 
> "You can't change the past, but you can ruin
> the present by worrying over the future"

-- 
Angel Luis Uruñuela <> Unix Systems Administrator

"You can't change the past, but you can ruin
the present by worrying over the future"



More information about the bind-users mailing list