Re: [TCLUG:5871] resolving multihomed ips

[Clay Fandre <cfandre@minn.net>]

After further investigation, I found out that the sortlist option is
only needed if the server isn't directly connected to your local network
(same subnet). We have our nameserver connected to all of our subnets,
so the sorting is done on the server, eliminating the need for the
clients to sort.

Clay

Clay Fandre wrote:
> 
> OK. I figured it out. For some reason (RH default?) in my
> /etc/nsswitch.conf file, the order of the hosts entry was:
> NIS DNS FILES
> which resulted in lookups to use NIS before DNS. That caused nslookup to
> work (since it always uses DNS) but other services used NIS to resolve
> hostnames, resulting in the wrong IP. After I switched the order to
> FILES DNS NIS
> everything seems to be working correctly.
> 
> Mark,
> It also works with the default glibc that comes with RH (both 5.2 and
> 6.0), and I didn't have to use the sortlist option in my resolv.conf.
> 
> I'm not really sure what the sortlist does. It seems to me it would
> break what I am trying to accomplish. I want my services to use the
> first IP returned by DNS, and doesn't sortlist order that list???
> 
> Clay Fandre
> 
> "Mark A. Bentley" wrote:
> >
> > On Fri, 7 May 1999, Clay Fandre wrote:
> > > /etc/hosts is empty except for the localhost, kramer, and DNS server. So
> > > it is resolving the name with the DNS server, but it is using the last
> > > IP it gets, instead of the first. Anyone have a multihomed server with
> > > this working? Both Slowaris and HS-UX works fine.
> > >
> > > Clay
> > >