[lug] host lookups

[D. Stimits]

Hugh Brown wrote:
> 
> I faked the entries for security purpose (i.e. they shouldn't have
> resolved at all).  I was just trying to emulate the host table without
> giving extra information.  I do not have an internal name server running
> so it must be going external and then failing.  ping and other network
> type functions work, it's just that exportfs takes far longer than it
> should.  I'll look into setting up an internal dns or fiddling with
> /etc/exports.

You can test the timeout theory (which is probably correct). Instead of
using a host name when doing your exportfs, use the exact ip address.

> 
> Thanks for the help.
> 
> Hugh
> 
> "D. Stimits" wrote:
> >
> > First, some notes...
> > (my nslookups use idcomm.com's name server)
> >
> > Hugh Brown wrote:
> > >
> > > HOSTNAME="juice"
> > >
> > > /etc/hosts
> > > 127.0.0.1       localhost       localhost.localdomain
> > > 192.168.1.1   juice.homenetwork.com          juice
> > nslookup finds this (interesting it is routable)
> >
> > > 192.168.1.2   host2.homenetwork.com          host2
> > nslookup finds this (interesting it is routable)
> >
> > > 192.168.1.3   host3.homenetwork.com          host3
> > > 192.168.1.4   host4.homenetwork.com          host4
> > > 192.168.1.5   host5.homenetwork.com          host5
> > The 3 above are not found by nslookup.
> >
> > My own box fails to find host for itself. This is probably the way it
> > should be. Maybe someone else can answer this...unless a non-routable
> > internal network has its own nameserver running for the
> > internal/unofficial ip's, then nameserver lookup will always go to the
> > outside world, and thus fail?
> >
> > Do you run your own nameserver? I suspect you can run ping juice or any
> > other name, and get an instant ping success. Probably it is only DNS
> > lookup that is failing via the host command.
> 
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug