On Fri, Apr 06, 2001 at 05:14:12PM +0200, Nathalie Boulos a ecrit:
>
> I executed:
> /usr/sbin/named-bootconf /etc/named.boot >> /etc/named.conf
This *appends* the result of the named-bootconf command to /etc/named.conf
(ie adds it to /etc/named.conf).
Try:
/usr/sbin/named-bootconf /etc/named.boot > /etc/named.conf
^
and it should be much better.
Apparently, there are several instances of named running on your system
as well as several network interfaces.
Is there a specific IP number you want named to fix itself to?
Do you want people on your internal network to be able to use
DNS records that other people shouldn't?
Try this:
service named stop (do this 2 or 3 times to make sure it works)
Check to see if /var/run/named.pid and /var/run/ndc exist.
You can rename them or move them to another directory if they do.
The /var/named directory should contain:
-rw-r--r-- 1 root root 187 jan 15 09:28 db.127.0.0
-rw-r--r-- 1 root root 1532 avr 1 02:15 db.cache
The contents of /etc/named.conf should be something like:
# Start of /etc/named.conf
options {
directory "/var/named";
fetch-glue no;
allow-transfer { IP.of.the.master.DNS.server; };
transfer-format many-answers;
};
zone "." in {
type hint;
file "db.cache";
};
zone "0.0.127.in-addr.arpa" in {
type master;
file "db.127.0.0";
};
zone "XXX.XXX.XXX.in-addr.arpa" in {
type slave;
file "db.XXX.XXX.XXX";
masters { IP.of.the.master.DNS.server; };
};
# End of /etc/named.conf
Replace XXX.XXX.XXX with the appropriate numbers and
IP.of.the.master.DNS.server then restart named.
Emmanuel Seyman
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
