Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!att!tut.cis.ohio-state.edu!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!mcsun!unido!opal!mailgzrz!elsn4000
From: elsn4000@mailgzrz.tu-berlin.de (Frank Elsner)
Newsgroups: comp.unix.sysv386
Subject: Re: TCP/NFS
Message-ID: <50@mailgzrz.tu-berlin.de>
Date: 23 Nov 90 06:51:21 GMT
References: <532@comcon.UUCP>
Sender: news@mailgzrz.tu-berlin.de
Organization: TUBerlin
Lines: 19
Nntp-Posting-Host: mailgzrz.tu-berlin.de

In article <532@comcon.UUCP> tim@comcon.UUCP (Tim Brown) writes:
>What it is doing now is pci complains about not being able to find my
>hostname in /etc/hosts (tho it is there) and the lockd complains about
>something similiar to do with the hostname being wrong.  Now the
>really weird part, if I telnet to one of the other hosts (a 6000)
>using the *internet* address it works but if I try to do it using the
>hostname, it hangs.  Ditto for ping.  If I ping another host using the
I would guess the problem is the Domain Name Service (DNS). Its usage is
activated by the file /etc/resolv.conf. If this file contains the one and
only line "nonameserver" you may run into the problems described.
File resolv.conf should contain on the first line the domain you're in and
in subsequent lines the IP addresses of the NameServers to ask.
 
My /etc/resolv.conf reads:
                            domain zrz.tu-berlin.de
                            nameserver 130.149.4.10
                            nameserver 130.149.5.4
 
Frank