Return to BSD News archive
Xref: sserve comp.protocols.tcp-ip:27934 comp.unix.bsd:13531 comp.unix.ultrix:21730 Newsgroups: comp.protocols.tcp-ip,comp.unix.bsd,comp.unix.ultrix Path: sserve!newshost.anu.edu.au!munnari.oz.au!bruce.cs.monash.edu.au!merlin!mel.dit.csiro.au!its.csiro.au!dmssyd.syd.dms.CSIRO.AU!metro!news.cs.su.oz.au!harbinger.cc.monash.edu.au!yeshua.marcam.com!MathWorks.Com!europa.eng.gtefsd.com!ulowell!wang!fitz From: fitz@wang.com (Tom Fitzgerald) Subject: Re: How do multi-homed hosts choose the interface? Organization: Wang Labs, Lowell MA, USA Date: Thu, 3 Mar 1994 02:21:04 GMT Message-ID: <CM2H75.7ww@wang.com> References: <2khb6f$9fl@breeze.dra.hmg.gb> Sender: news@wang.com Nntp-Posting-Host: fnord.wang.com Lines: 23 heading@signal.dra.hmg.gb (Anthony Heading) writes: > I want the two routing machines to use the FDDI network to > talk to each other, but they steadfastly refuse to use anything > but the ethernet. > This makes me suspect that multiple A records > are used by trying each address in the gethostbyjingo() structure > in turn, but there seems to be no way of making the DNS server > impose order onto those addresses. Isn't this what the "sortlist" directive in named.boot is supposed to do? Try sticking it on your nameserver. The disadvantage to sortlist is that if your ethernet has routers to nets other than the fddi net, then traffic to one of the multihomed systems may go outside->router->ether->one-fddi-host->fddi->other-fddi-host, even though the other-fddi-host has a leg on the ethernet. This depends on which multihomed host is preferred as a route to the fddi. -- Tom Fitzgerald Wang Labs Lowell MA, USA 1-508-967-5278 fitz@wang.com Pardon me, I'm lost, can you direct me to the information superhighway?