Re: [LUG] NFS, /etc/resolv.conf rather odd connection.

[Andrew Rogers <andrew@xxxxxxxxxxxxxxxx>]

Neil Stone wrote:

> Neil Williams wrote:
>
> > On Thursday 06 Nov 2003 10:05 pm, Neil Stone wrote:
> >
> > > Neil Williams wrote:
> > >
> > > > On Thursday 06 Nov 2003 8:19 pm, Andrew Rogers wrote:
> > > >
> > > > > behaves perfectly with no long delays.
> > > >
> > > >
> > > > DNS timeout?
> > >
> > >
> > > the machine was unable to contact its default route... stupid or what ?
> >
> >
> >
> > Same thought was in the back of my mind.
> >
> > Check the route on the machine trying to export the NFS mount.
> >
> > A bad gateway setting would cause the DNS to timeout. Removing 
> > /etc/resolv.conf only solves the problem by preventing NFS from using 
> > DNS.
> >
> > As you said, Andrew:
> >  I known that from a previous setup incorrect DNS servers cause this 
> > problem.
> >
> > The problem is finding out which bit of the DNS setup is 
> > missing/failing.
>
> Er.. use nslookup....
>
> Ensure that both the NFS client and server are able to reach their 
> default route, try pinging it.. (run "route -n")
>
>
> --
> The Mailing List for the Devon & Cornwall LUG
> Mail majordomo@xxxxxxxxxxxx with "unsubscribe list" in the
> message body to unsubscribe.
All entries in /etc/resolv.conf were check with nslookup and only 
127.0.0.1 failed. Should the loopback appear in /etc/resolv.conf? If I 
run nslookup without specifying a DNS the nslookup suceeds because a 
valid DNS is chosen automatically.

What I am now wondering is that the DNS may do a lookup but not a 
reverse lookup, a reverse lookup was mentioned earlier. I'll investigate.

Thanks
Andrew



--
The Mailing List for the Devon & Cornwall LUG
Mail majordomo@xxxxxxxxxxxx with "unsubscribe list" in the
message body to unsubscribe.