On Thu, 15 Mar 2001, Martin Sieben spewed into the bitstream:
MS>in resolv.conf replace 127. with real IP. That may help
Or how about putting in a DNS record for loclhost? A lot of people omit
that and it causes problems.
MS>On Thu, 15 Mar 2001, Nathalie Boulos wrote:
MS>
MS>> Hi,
MS>>
MS>> I have two RHL6.2 servers on a LAN, named is started on both servers. They
MS>> are cache servers for DNS on the WAN.
MS>> The original problem is that when I try accessing the servers by telnet or
MS>> ftp, or event to check emails, they do not reply instantly, though they are
MS>> on the same ethernet segment I'm working on.
MS>> I want to solve that problem. Does anyone know what this might be????
MS>>
MS>> I discovered the nslookup error this morning:
MS>> The two linux have the same resolv.conf file. One of the servers is giving
MS>> the error:
MS>> ***Can't find server name for address 127.0.0.1 : No response from server
MS>>
MS>> when I execute on that server:
MS>> #ps aux | grep named
MS>> I get the process "named -u named"
MS>>
MS>> If I execute the same command on the other server I get: /usr/sbin/named
MS>> because I executed
MS>> #ndc start
MS>>
MS>> Can anyone tell me what's the problem? And is the DNS causing the late reply
MS>> of my servers?
--
Chuck Mead, csm -AT- moongroup.com, Owner, MoonGroup.com
(Note: html formatted email sent to me is filtered & deleted unread)
GnuPG Public Key Available: http://wwwkeys.us.pgp.net
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
