On Thu, 15 Mar 2001, Nathalie Boulos wrote:
> I have two RHL6.2 servers on a LAN, named is started on both servers. They
> are cache servers for DNS on the WAN.
> The original problem is that when I try accessing the servers by telnet or
> ftp, or event to check emails, they do not reply instantly, though they are
> on the same ethernet segment I'm working on.
> I want to solve that problem. Does anyone know what this might be????
>
> I discovered the nslookup error this morning:
> The two linux have the same resolv.conf file. One of the servers is giving
> the error:
> ***Can't find server name for address 127.0.0.1 : No response from server
>
> when I execute on that server:
> #ps aux | grep named
> I get the process "named -u named"
>
> If I execute the same command on the other server I get: /usr/sbin/named
> because I executed
> #ndc start
>
> Can anyone tell me what's the problem? And is the DNS causing the late reply
> of my servers?
>
> I would greatly appreciate any help.
> Sincerely
> Nathalie
>
The problem is that your local name server doesn't have a reverse DNS
listing for 127.0.0.1, so when it trys to look up its own name when it
is answering on 127.0.0.1, it doesn't get an answer. One way to fix it
is to add one more zone file to your /etc/named.conf file.
zone "0.0.127.IN-ADDR.ARPA" {
notify no;
type master;
file "db.127.0.0";
};
and the db.127.0.0 file could look like this:
$TTL 1d
@ IN SOA localhost. root.localhost. (
2000080601 ; serial
10800 ; refresh
3600 ; retry
604800 ; expire
86400 ) ; Minimum TTL
IN NS localhost.
1 IN PTR localhost.
Mikkel
--
Do not meddle in the affairs of dragons,
for you are crunchy and taste good with ketchup.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
