我这里列出下列配置文件。想麻烦各位帮我分析一下。问题在哪里
这个是name.conf
下列为db.fot.com// This is the primary configuration file for the BIND DNS server named.
//
// Please read /usr/share/doc/bind9/README.Debian.gz for information on the
// structure of BIND configuration files in Debian, *BEFORE* you customize
// this configuration file.
//
// If you are just adding zones, please do that in /etc/bind/named.conf.local
include "/etc/bind/named.conf.options";
// prime the server with knowledge of the root servers
zone "." {
type hint;
file "/etc/bind/db.root";
};
// be authoritative for the localhost forward and reverse zones, and for
// broadcast zones as per RFC 1912
zone "localhost" {
type master;
file "/etc/bind/db.local";
};
zone "127.in-addr.arpa" {
type master;
file "/etc/bind/db.127";
};
zone "0.in-addr.arpa" {
type master;
file "/etc/bind/db.0";
};
zone "255.in-addr.arpa" {
type master;
file "/etc/bind/db.255";
};
zone "33.168.192.in-addr.arpa" {
type master;
file "/etc/bind/db.dns";
};
// zone "com" { type delegation-only; };
// zone "net" { type delegation-only; };
// From the release notes:
// Because many of our users are uncomfortable receiving undelegated answers
// from root or top level domains, other than a few for whom that behaviour
// has been trusted and expected for quite some length of time, we have now
// introduced the "root-delegations-only" feature which applies delegation-only
// logic to all top level domains, and to the root domain. An exception list
// should be specified, including "MUSEUM" and "DE", and any other top level
// domains from whom undelegated responses are expected and trusted.
// root-delegation-only exclude { "DE"; "MUSEUM"; };
include "/etc/bind/named.conf.local";
key "rndc-key" {
algorithm hmac-md5;
secret "f6O3asXZ9SnBvbowFQwMBQ==";
};
controls {
inet 127.0.0.1 port 953
allow { 127.0.0.1; } keys { "rndc-key"; };
};
named.conf.local;
; BIND data file for local loopback interface
;
$TTL 604800
@ IN SOA dark.fot.com. dark.fot.com. (
1 ; Serial
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
604800 ) ; Negative Cache TTL
;
@ IN NS dark.fot.com.
@ IN A 192.168.33.86
@ IN MX 10 dark.fot.com.
dark.fot.com. IN A 192.168.33.86
www.fot.com. in chame dark.fot.com.
ftp.fot.com. in chame dark.fot.com.
zabbix.fot.com. in chame dark.fot.com.
named.conf.options//
// Do any local configuration here
//
// Consider adding the 1918 zones here, if they are not used in your
// organization
//include "/etc/bind/zones.rfc1918";
zone "fot.com" {
type master;
file "/etc/bind/db.fot.com";
};
运行rndc status后显示options {
directory "/var/cache/bind";
// 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 and later use an unprivileged
// port by default.
// query-source address * port 53;
// If your ISP provided one or more IP addresses for stable
// nameservers, you probably want to use them as forwarders.
// Uncomment the following block, and insert the addresses replacing
// the all-0's placeholder.
forwarders {
202.96.209.133;
202.96.209.5;
};
auth-nxdomain no; # conform to RFC1035
listen-on-v6 { any; };
allow-query { any; };
};
重启binddark@dark:/etc/bind$ rndc status
number of zones: 16
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is OFF
recursive clients: 0/0/1000
tcp clients: 0/100
server is up and running
dark@dark:/etc/bind$
dark@dark:/etc/bind$ sudo /etc/init.d/bind9 restart
* Stopping domain name service... bind [ OK ]
* Starting domain name service... bind [ OK ]
dark@dark:/etc/bind$
运行nslookup
dark@dark:/etc/bind$ nslookup dark.fot.com
Server: 192.168.33.86
Address: 192.168.33.86#53
** server can't find dark.fot.com: SERVFAIL
dark@dark:/etc/bind$