Date: Mon, 07 Aug 1995 18:11:09 -0700 From: "Justin T. Gibbs" <gibbs@freefall.cdrom.com> To: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> Cc: gary@palmer.demon.co.uk (Gary Palmer), jkh@time.cdrom.com, freebsd-current@freebsd.org, joerg_wunsch@uriah.heep.sax.de Subject: Re: workaround for talk's address problem Message-ID: <199508080111.SAA12458@freefall.cdrom.com> In-Reply-To: Your message of "Mon, 07 Aug 95 17:43:16 PDT." <199508080043.RAA02014@gndrsh.aac.dev.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>>
>> In message <199508080002.RAA01756@gndrsh.aac.dev.com>, "Rodney W. Grimes" wr
>ite
>> As Jsutin already stated, you run named on gndrsh, so when a client
>> does a nslookup of gndrsh to find it's address, it'll get the address
>> of the interface it connects to ('cos BIND is like that). However,
>> morton/throck don't run nameservers, who does the nameservice, and
>> hence the address could be returned in a random order. If the slip
>> addr is returned first, then mount will try and contact the slip
>> address. mountd will reply from the ether address and confuse the
>> client.
>>
>> Does this clear things up? :-)
>
>Yes, but leads to a simple fix, running a cacheing name server on all
>NFS servers, and point your clients to that name server.
It only works if the multi-homed host that is running named is local to
the client. If I'm in Japan and I try to access a multi-homed NFS server
in New York, I'm screwed no matter which name server I use.
>--
>Rod Grimes rgrimes@gndrsh.aac.dev.com
>Accurate Automation Company Reliable computers for FreeBSD
--
Justin T. Gibbs
===========================================
Software Developer - Walnut Creek CDROM
FreeBSD: Turning PCs into workstations
===========================================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199508080111.SAA12458>