由 emylekao 在 11-03-2004 12:20 发表:
帮帮忙，DNS安装成功，运行出错？
提示信息
/usr/local/sbin/named -gc /etc/namedb/named.conf
03-Nov-2004 20:01:37.183 starting BIND 9.3.0 -gc /etc/namedb/named.conf
03-Nov-2004 20:01:37.197 loading configuration from '/etc/namedb/named.conf'
03-Nov-2004 20:01:37.199 listening on IPv4 interface lnc0, 192.168.1.123#53
03-Nov-2004 20:01:37.206 listening on IPv4 interface lo0, 127.0.0.1#53
03-Nov-2004 20:01:37.221 command channel listening on 127.0.0.1#953
03-Nov-2004 20:01:37.221 ignoring config file logging statement due to -g option03-Nov-2004 20:01:37.235 zone 0.0.127.IN-ADDR.ARPA/IN: loaded serial 20041103
03-Nov-2004 20:01:37.242 zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA/IN: loaded serial 20041103
03-Nov-2004 20:01:37.268 s/test.com.bak:4: unknown RR type 'server1.test.com.'
03-Nov-2004 20:01:37.273 zone test.com/IN: loading master file s/test.com.bak: unknown class/type
03-Nov-2004 20:01:37.278 zone test.com/IN: saved 's/test.com.bak' as 's/db-P9fufe1r'
03-Nov-2004 20:01:37.299 zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.INT/IN: loaded serial 20041103
03-Nov-2004 20:01:37.305 running
03-Nov-2004 20:01:37.824 zone test.com/IN: refresh: unexpected rcode (SERVFAIL) from master 192.168.1.123#53 (source 0.0.0.0#0)
test.com域名添加有问题，具体应该怎样呢？我不太明白。
运行环境：freebsd4.10，bind9。
关于Python/PHP、Linux和FreeBSD。
Linux/FreeBSD忠实爱好者
希望对推动Linux在中国的发展略尽微薄之力。
Fedora core 2 & FreeBSD 4.10
由 gmx_163 在 11-03-2004 12:24 发表:
unknown RR type 'server1.test.com.'
这不是提醒你了，在文件中没指定，先添加上，再看还有什么错误
由 emylekao 在 11-03-2004 12:56 发表:
对不起，对bind一点都不熟悉。应该把那个加在哪里呢？
关于Python/PHP、Linux和FreeBSD。
Linux/FreeBSD忠实爱好者
希望对推动Linux在中国的发展略尽微薄之力。
Fedora core 2 & FreeBSD 4.10
由 emylekao 在 11-03-2004 13:01 发表:
我看到其他帖子里面，都没有提到RR这个东西啊。
关于Python/PHP、Linux和FreeBSD。
Linux/FreeBSD忠实爱好者
希望对推动Linux在中国的发展略尽微薄之力。
Fedora core 2 & FreeBSD 4.10
由 gmx_163 在 11-03-2004 17:29 发表:
不明白,你把配置文件发上来吧
由 emylekao 在 11-03-2004 19:50 发表:
cat /etc/namedb/named.conf
// $FreeBSD: src/etc/namedb/named.conf,v 1.6.2.7 2003/02/13 13:16:51 keramida Exp $
//
// Refer to the named.conf(5) and named(8) man pages for details. If
// you are ever going to set up a primary server, make sure you
// understand the hairy details of how DNS works. Even with
// simple mistakes, you can break connectivity for affected parties,
// or cause huge amounts of useless Internet traffic.
options {
directory "/etc/namedb";
// In addition to the "forwarders" clause, you can force your name
// server to never initiate queries of its own, but always ask its
// forwarders only, by enabling the following line:
//
// forward only;
// If you've got a DNS server around at your upstream provider, enter
// its IP address here, and enable the line below. This will make you
// benefit from its cache, thus reduce overall DNS traffic in the Internet.
/*
forwarders {
127.0.0.1;
};
*/
/*
If there is a firewall between you and nameservers you want
to talk to, you might need to uncomment the query-source
directive below. Previous versions of BIND always asked
questions using port 53, but BIND 8.1 uses an unprivileged
port by default.
*/
// query-source address * port 53;
/*
If running in a sandbox, you may have to specify a different
location for the dumpfile.
*/
// dump-file "s/named_dump.db";
};
// Note: the following will be supported in a future release.
/*
host { any; } {
topology {
127.0.0.0/8;
};
};
*/
// Setting up secondaries is way easier and a rough example for this
// is provided below.
//
// If you enable a local name server, don't forget to enter 127.0.0.1
// first in your /etc/resolv.conf so this server will be queried.
// Also, make sure to enable it in /etc/rc.conf.
zone "." {
type hint;
file "named.root";
};
zone "0.0.127.IN-ADDR.ARPA" {
type master;
file "localhost.rev";
};
// RFC 3152
zone "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA" {
type master;
file "localhost-v6.rev";
};
// RFC 1886 -- deprecated
zone "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.INT" { type master;
file "localhost-v6.rev";
};
// NB: Do not use the IP addresses below, they are faked, and only
// serve demonstration/documentation purposes!
//
// Example secondary config entries. It can be convenient to become
// a secondary at least for the zone your own domain is in. Ask
// your network administrator for the IP address of the responsible
// primary.
//
// Never forget to include the reverse lookup (IN-ADDR.ARPA) zone!
// (This is named after the first bytes of the IP address, in reverse
// order, with ".IN-ADDR.ARPA" appended.)
//
// Before starting to set up a primary zone, make sure you fully
// understand how DNS and BIND works. There are sometimes
// non-obvious pitfalls. Setting up a secondary is simpler.
//
// NB: Don't blindly enable the examples below. :-) Use actual names
// and addresses instead.
//
// NOTE!!! FreeBSD ca