linux下bind服务器的问题

cnhawk386

linux下bind服务器的问题
在2003下  自己瞎起域名可以正常解析
而且可以用自己瞎起的域名发邮件呢
linux下  外网域名可以正常的解析
自己瞎起的域名却无法解析
错误提示为:server can't find xsb: NXDOMAIN

cnhawk386

听说linuxsir 的成员很热心啊

cnhawk386

linux下bind服务器的问题
在2003下  自己瞎起域名可以正常解析
而且可以用自己瞎起的域名发邮件呢
linux下  外网域名可以正常的解析
自己瞎起的域名却无法解析
错误提示为:server can't find xsb: NXDOMAIN
发表于:2007-4-11 14:51　
--------------------------------------------------------------------------------
named.conf文件内容如下:
// Default named.conf generated by install of bind-9.2.4-2
options {
        directory "/var/named";
        dump-file "/var/named/data/cache_dump.db";
        statistics-file "/var/named/data/named_stats.txt";
};
include "/etc/rndc.key";
zone "." {
type hint;
file "named.ca";
};
zone "0.0.127.in-addr.arpa" {
type master;
file "127.0.0";
};
zone "wb.wzy" {
type master;
file "wb.wzy";
};
zone "0.168.192.in-addr.arpa" {
type master;
file "192.168.0";
};
wb.wzy文件内容如下:
@ IN SOA xsb.wb.wzy. root.xsb.wb.wzy. (
2000051500 ; Serial
28800 ; Refresh
14400 ; Retry
3600000 ; Expire
86400 ) ; Minimum
IN NS 192.168.0.11
xsb.wb.wzy. IN  A 192.168.0.11
gyb.wb.wzy. IN A 192.168.0.5

cnhawk386

听说linuxsir高人不少 啊

captail

wb.wzy文件内容中的
IN NS 192.168.0.11
这个IP地址应该是写nameserver的名称吧.

cnhawk386

bind?????????????


named.conf// Default named.conf generated by install of bind-9.2.4-2
options {
        directory "/var/named";
        dump-file "/var/named/data/cache_dump.db";
        statistics-file "/var/named/data/named_stats.txt";
};
include "/etc/rndc.key";

zone "." {
type hint;
file "named.ca";　　
};

zone "0.0.127.in-addr.arpa" {
type master;
file "127.0.0";
};

zone "wb.wzy" {
type master;
file "wb.wzy";
};


错误提示:


tarting named: /etc/named.conf:11: unknown option '　　'
/etc/named.conf:12: unexpected token near '}'

Apr 17 11:51:36.087 starting BIND 9.2.4 -g
Apr 17 11:51:36.087 using 1 CPU
Apr 17 11:51:36.094 loading configuration from '/etc/named.conf'
Apr 17 11:51:36.094 /etc/named.conf:11: unknown option '　　'
Apr 17 11:51:36.094 /etc/named.conf:12: unexpected token near '}'
Apr 17 11:51:36.094 loading configuration: unexpected token
Apr 17 11:51:36.094 exiting (due to fatal error)