FreeBSD 7.2里设定DNS

bedreaming

先把那几个permission denied给搞定吧

llzqq

原帖由 unix3er 于 2009-8-26 08:55 发表
谢谢.

好像问题还有不少.请看下面:

$ named -gc /var/named/etc/namedb/named.conf
25-Aug-2009 17:51:52.076 starting BIND 9.4.3-P2 -gc /var/named/etc/namedb/named.conf
25-Aug-2009 17:51:52.076 ...

我晕，不是说了让你用ROOT用户启动named吗，怎么就不听呢。。。

ruochen

named的目录和其下的文件的权限先搞定

unix3er

原帖由 llzqq 于 2009-8-26 18:28 发表



我晕，不是说了让你用ROOT用户启动named吗，怎么就不听呢。。。

抱歉.重新登入后,忘记使用ROOT了.log如下: 请看是否正常,我还没有做反向解析.
x14# named -gc /var/named/etc/namedb/named.conf
26-Aug-2009 17:54:54.405 starting BIND 9.4.3-P2 -gc /var/named/etc/namedb/named.conf
26-Aug-2009 17:54:54.405 found 2 CPUs, using 2 worker threads
26-Aug-2009 17:54:54.405 using up to 4096 sockets
26-Aug-2009 17:54:54.412 loading configuration from '/var/named/etc/namedb/named.conf'
26-Aug-2009 17:54:54.415 using default UDP/IPv4 port range: [49152, 65535]
26-Aug-2009 17:54:54.415 using default UDP/IPv6 port range: [49152, 65535]
26-Aug-2009 17:54:54.417 listening on IPv4 interface bge0, 192.168.0.14#53
26-Aug-2009 17:54:54.418 listening on IPv4 interface lo0, 127.0.0.1#53
26-Aug-2009 17:54:54.422 zone '168.192.in-addr.arpa' allows updates by IP address, which is insecure
26-Aug-2009 17:54:54.422 zone '168.192.in-addr.arpa' allows updates by IP address, which is insecure
26-Aug-2009 17:54:54.434 command channel listening on 127.0.0.1#953
26-Aug-2009 17:54:54.434 ignoring config file logging statement due to -g option
26-Aug-2009 17:54:54.435 zone 0.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.436 zone 10.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.436 zone 127.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.436 zone 254.169.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.436 zone 16.172.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.437 zone 17.172.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.437 zone 18.172.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.437 zone 19.172.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.437 zone 20.172.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.438 zone 21.172.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.438 zone 22.172.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.438 zone 23.172.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.438 zone 24.172.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.439 zone 25.172.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.439 zone 26.172.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.439 zone 27.172.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.439 zone 28.172.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.440 zone 29.172.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.440 zone 30.172.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.440 zone 31.172.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.440 zone 2.0.192.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.441 zone 168.192.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.441 zone 18.198.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.441 zone 19.198.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.442 zone 240.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.442 zone 241.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.442 zone 242.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.442 zone 243.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.442 zone 244.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.443 zone 245.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.443 zone 246.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.443 zone 247.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.444 zone 248.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.444 zone 249.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.444 zone 250.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.445 zone 251.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.445 zone 252.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.445 zone 253.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.446 zone 254.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.446 zone 255.in-addr.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.446 zone 0.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.447 zone 1.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.447 zone 3.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.447 zone 4.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.447 zone 5.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.448 zone 6.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.448 zone 7.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.448 zone 8.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.448 zone 9.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.448 zone a.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.449 zone b.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.449 zone c.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.449 zone d.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.449 zone e.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.450 zone 0.f.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.450 zone 1.f.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.450 zone 2.f.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.450 zone 3.f.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.451 zone 4.f.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.451 zone 5.f.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.451 zone 6.f.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.451 zone 7.f.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.452 zone 8.f.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.452 zone 9.f.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.452 zone a.f.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.452 zone b.f.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.453 zone c.f.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.453 zone d.f.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.453 zone 0.e.f.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.453 zone 1.e.f.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.454 zone 2.e.f.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.454 zone 3.e.f.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.454 zone 4.e.f.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.454 zone 5.e.f.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.455 zone 6.e.f.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.455 zone 7.e.f.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.455 zone 8.e.f.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.455 zone 9.e.f.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.455 zone a.e.f.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.456 zone b.e.f.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.456 zone c.e.f.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.456 zone d.e.f.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.456 zone e.e.f.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.457 zone f.e.f.ip6.arpa/IN: loaded serial 42
26-Aug-2009 17:54:54.457 zone qd-huanhai.com/IN: loaded serial 2008082000
26-Aug-2009 17:54:54.457 zone ip6.int/IN: loaded serial 42
26-Aug-2009 17:54:54.458 zone localhost/IN: loaded serial 42
26-Aug-2009 17:54:54.460 running
26-Aug-2009 17:54:54.460 zone qd-huanhai.com/IN: sending notifies (serial 2008082000)
26-Aug-2009 17:55:40.248 host unreachable resolving 'ns1.apnic.net/A/IN': 2001:500:1::803f:235#53
26-Aug-2009 17:55:40.248 host unreachable resolving 'ns3.apnic.net/A/IN': 2001:500:1::803f:235#53
26-Aug-2009 17:55:40.249 host unreachable resolving 'ns1.apnic.net/AAAA/IN': 2001:500:1::803f:235#53
26-Aug-2009 17:55:40.249 host unreachable resolving 'ns3.apnic.net/AAAA/IN': 2001:500:1::803f:235#53
26-Aug-2009 17:55:40.250 host unreachable resolving 'ns4.apnic.net/A/IN': 2001:500:1::803f:235#53
26-Aug-2009 17:55:40.250 host unreachable resolving 'ns4.apnic.net/AAAA/IN': 2001:500:1::803f:235#53
26-Aug-2009 17:55:40.250 host unreachable resolving 'ns-sec.ripe.net/A/IN': 2001:500:1::803f:235#53
26-Aug-2009 17:55:40.251 host unreachable resolving 'ns-sec.ripe.net/AAAA/IN': 2001:500:1::803f:235#53
26-Aug-2009 17:55:40.251 host unreachable resolving 'tinnie.arin.net/A/IN': 2001:500:1::803f:235#53
26-Aug-2009 17:55:40.251 host unreachable resolving 'tinnie.arin.net/AAAA/IN': 2001:500:1::803f:235#53
26-Aug-2009 17:55:44.062 host unreachable resolving 'M.GTLD-SERVERS.net/A/IN': 2001:7fd::1#53
26-Aug-2009 17:55:44.062 host unreachable resolving 'M.GTLD-SERVERS.net/AAAA/IN': 2001:7fd::1#53
26-Aug-2009 17:55:44.864 host unreachable resolving 'M.GTLD-SERVERS.net/A/IN': 2001:503:c27::2:30#53
26-Aug-2009 17:55:44.864 host unreachable resolving 'M.GTLD-SERVERS.net/AAAA/IN': 2001:503:c27::2:30#53
26-Aug-2009 17:55:44.865 host unreachable resolving 'M.GTLD-SERVERS.net/A/IN': 2001:500:2f::f#53
26-Aug-2009 17:55:44.865 host unreachable resolving 'M.GTLD-SERVERS.net/AAAA/IN': 2001:500:2f::f#53
26-Aug-2009 17:55:45.952 host unreachable resolving 'c3.nstld.com/A/IN': 2001:500:2f::f#53
26-Aug-2009 17:55:45.952 host unreachable resolving 'd3.nstld.com/A/IN': 2001:500:2f::f#53
26-Aug-2009 17:55:45.952 host unreachable resolving 'c3.nstld.com/AAAA/IN': 2001:500:2f::f#53
26-Aug-2009 17:55:45.952 host unreachable resolving 'd3.nstld.com/AAAA/IN': 2001:500:2f::f#53
26-Aug-2009 17:55:45.953 host unreachable resolving 'm3.nstld.com/A/IN': 2001:500:2f::f#53
26-Aug-2009 17:55:45.953 host unreachable resolving 'm3.nstld.com/AAAA/IN': 2001:500:2f::f#53
26-Aug-2009 17:55:46.754 host unreachable resolving 'c3.nstld.com/A/IN': 2001:503:c27::2:30#53
26-Aug-2009 17:55:46.754 host unreachable resolving 'd3.nstld.com/A/IN': 2001:503:c27::2:30#53
26-Aug-2009 17:55:46.754 host unreachable resolving 'c3.nstld.com/AAAA/IN': 2001:503:c27::2:30#53
26-Aug-2009 17:55:46.755 host unreachable resolving 'd3.nstld.com/AAAA/IN': 2001:503:c27::2:30#53
26-Aug-2009 17:55:46.755 host unreachable resolving 'm3.nstld.com/A/IN': 2001:503:c27::2:30#53
26-Aug-2009 17:55:46.755 host unreachable resolving 'm3.nstld.com/AAAA/IN': 2001:503:c27::2:30#53
26-Aug-2009 17:55:46.755 host unreachable resolving 'c3.nstld.com/A/IN': 2001:7fd::1#53
26-Aug-2009 17:55:46.755 host unreachable resolving 'c3.nstld.com/AAAA/IN': 2001:7fd::1#53
26-Aug-2009 17:55:46.755 host unreachable resolving 'd3.nstld.com/A/IN': 2001:7fd::1#53
26-Aug-2009 17:55:46.755 host unreachable resolving 'm3.nstld.com/A/IN': 2001:7fd::1#53
26-Aug-2009 17:55:46.756 host unreachable resolving 'd3.nstld.com/AAAA/IN': 2001:7fd::1#53
26-Aug-2009 17:55:46.756 host unreachable resolving 'm3.nstld.com/AAAA/IN': 2001:7fd::1#53
26-Aug-2009 17:55:48.981 host unreachable resolving 'c3.nstld.com/A/IN': 2001:503:231d::2:30#53
26-Aug-2009 17:55:48.981 host unreachable resolving 'c3.nstld.com/AAAA/IN': 2001:503:231d::2:30#53
26-Aug-2009 17:55:48.983 host unreachable resolving 'd3.nstld.com/A/IN': 2001:503:231d::2:30#53
26-Aug-2009 17:55:48.983 host unreachable resolving 'm3.nstld.com/A/IN': 2001:503:231d::2:30#53
26-Aug-2009 17:55:48.985 host unreachable resolving 'd3.nstld.com/AAAA/IN': 2001:503:231d::2:30#53
26-Aug-2009 17:55:48.985 host unreachable resolving 'm3.nstld.com/AAAA/IN': 2001:503:231d::2:30#53
26-Aug-2009 17:55:50.242 host unreachable resolving 'a2.nstld.com/A/IN': 2001:dc3::35#53
26-Aug-2009 17:55:50.242 host unreachable resolving 'd2.nstld.com/A/IN': 2001:dc3::35#53
26-Aug-2009 17:55:50.242 host unreachable resolving 'a2.nstld.com/AAAA/IN': 2001:dc3::35#53
26-Aug-2009 17:55:50.242 host unreachable resolving 'd2.nstld.com/AAAA/IN': 2001:dc3::35#53
26-Aug-2009 17:55:50.243 host unreachable resolving 'e2.nstld.com/A/IN': 2001:dc3::35#53
26-Aug-2009 17:55:50.243 host unreachable resolving 'e2.nstld.com/AAAA/IN': 2001:dc3::35#53
26-Aug-2009 17:55:50.244 host unreachable resolving 'g2.nstld.com/A/IN': 2001:dc3::35#53
26-Aug-2009 17:55:50.244 host unreachable resolving 'f2.nstld.com/A/IN': 2001:dc3::35#53
26-Aug-2009 17:55:50.244 host unreachable resolving 'g2.nstld.com/AAAA/IN': 2001:dc3::35#53
26-Aug-2009 17:55:50.244 host unreachable resolving 'f2.nstld.com/AAAA/IN': 2001:dc3::35#53
26-Aug-2009 17:55:50.245 host unreachable resolving 'c2.nstld.com/A/IN': 2001:dc3::35#53
26-Aug-2009 17:55:50.245 host unreachable resolving 'h2.nstld.com/A/IN': 2001:dc3::35#53
26-Aug-2009 17:55:50.245 host unreachable resolving 'c2.nstld.com/AAAA/IN': 2001:dc3::35#53
26-Aug-2009 17:55:50.245 host unreachable resolving 'h2.nstld.com/AAAA/IN': 2001:dc3::35#53
26-Aug-2009 17:55:50.246 host unreachable resolving 'l2.nstld.com/A/IN': 2001:dc3::35#53
26-Aug-2009 17:55:50.246 host unreachable resolving 'l2.nstld.com/AAAA/IN': 2001:dc3::35#53
26-Aug-2009 17:59:29.724 host unreachable resolving '238.224.166.119.in-addr.arpa/PTR/IN': 2001:503:ba3e::2:30#53
26-Aug-2009 17:59:33.593 host unreachable resolving '238.224.166.119.in-addr.arpa/PTR/IN': 2001:dc0:2001:0:4608::25#53
26-Aug-2009 17:59:33.593 host unreachable resolving '238.224.166.119.in-addr.arpa/PTR/IN': 2001:dc0:1:0:4777::131#53
26-Aug-2009 17:59:33.594 host unreachable resolving '238.224.166.119.in-addr.arpa/PTR/IN': 2001:610:240:0:53::4#53
26-Aug-2009 17:59:42.450 host unreachable resolving 'ns.sdjnptt.net.cn/AAAA/IN': 2001:dc7:1000::1#53
26-Aug-2009 17:59:42.450 host unreachable resolving 'ns1.sdqdptt.net.cn/AAAA/IN': 2001:dc7:1000::1#53
26-Aug-2009 17:59:42.452 host unreachable resolving 'ns.sdjnptt.net.cn/A/IN': 2001:dc7:1000::1#53
26-Aug-2009 17:59:42.454 host unreachable resolving 'ns1.sdqdptt.net.cn/A/IN': 2001:dc7:1000::1#53
26-Aug-2009 18:02:38.650 unexpected RCODE (REFUSED) resolving 'ns.bta.net.cn/A/IN': 202.106.196.233#53
26-Aug-2009 18:02:38.653 unexpected RCODE (REFUSED) resolving 'ns.bta.net.cn/AAAA/IN': 202.106.196.233#53
26-Aug-2009 18:07:58.440 host unreachable resolving '36.211.142.98.in-addr.arpa/PTR/IN': 2001:440:2000:1::21#53
26-Aug-2009 18:08:07.055 host unreachable resolving 'DNS1.WIRESIX.COM/A/IN': 2001:503:a83e::2:30#53
26-Aug-2009 18:08:07.055 host unreachable resolving 'DNS2.WIRESIX.COM/A/IN': 2001:503:a83e::2:30#53
26-Aug-2009 18:08:07.057 host unreachable resolving 'DNS1.WIRESIX.COM/AAAA/IN': 2001:503:a83e::2:30#53
26-Aug-2009 18:08:07.057 host unreachable resolving 'DNS2.WIRESIX.COM/AAAA/IN': 2001:503:a83e::2:30#53
26-Aug-2009 18:10:39.009 host unreachable resolving 'ns.guangzhou.gd.cn/A/IN': 2001:dc7::1#53
26-Aug-2009 18:10:39.009 host unreachable resolving 'dns.guangzhou.gd.cn/A/IN': 2001:dc7::1#53
26-Aug-2009 18:10:39.009 host unreachable resolving 'ns.guangzhou.gd.cn/AAAA/IN': 2001:dc7::1#53
26-Aug-2009 18:10:39.009 host unreachable resolving 'dns.guangzhou.gd.cn/AAAA/IN': 2001:dc7::1#53
26-Aug-2009 18:11:06.100 host unreachable resolving '27.100.150.211.in-addr.arpa/PTR/IN': 2001:500:1::803f:235#53
26-Aug-2009 18:13:06.370 host unreachable resolving '97.220.94.125.in-addr.arpa/PTR/IN': 2001:500:13::c7d4:35#53
26-Aug-2009 18:13:06.371 host unreachable resolving '97.220.94.125.in-addr.arpa/PTR/IN': 2001:13c7:7002:3000::11#53
26-Aug-2009 18:13:06.371 host unreachable resolving '97.220.94.125.in-addr.arpa/PTR/IN': 2001:dc0:4001:1:0:1836:0:140#53

unix3er

原帖由 ruochen 于 2009-8-26 18:50 发表
named的目录和其下的文件的权限先搞定

谢谢.

应该是我用错账号造成的.

llzqq

这不是能运行了吗，

那些“host unreachable resolving”，应该检查一下你的DNS服务器与INTERNET有可靠连接吗，resolv.conf里面配置了外网DNS了吗。

bedreaming

原帖由 llzqq 于 2009-8-27 10:41 发表
这不是能运行了吗，

那些“host unreachable resolving”，应该检查一下你的DNS服务器与INTERNET有可靠连接吗，resolv.conf里面配置了外网DNS了吗。

那个是IPV6不可达造成的，应该是它的bind支持IPV6，但网络不支持。
用named -4启动应该就不会有这些东东了。

unix3er

谢谢两位,

使用 named -4后,果然没有 unreachable 这个提示.

但是多出来如下的提示(以前没有这个提示)

27-Aug-2009 00:58:49.799 lame server resolving 'images.golfsmith.com.usgcac.txcdn.net' (in 'usgcac.txcdn.NET'?): 121.52.215.6#53
27-Aug-2009 00:58:49.820 lame server resolving 'images.golfsmith.com.usgcac.txcdn.net' (in 'usgcac.txcdn.NET'?): 121.52.215.6#53
27-Aug-2009 00:58:49.875 lame server resolving 'images.golfsmith.com.usgcac.txcdn.net' (in 'usgcac.txcdn.NET'?): 58.63.244.114#53
27-Aug-2009 01:18:23.356 lame server resolving 'images.golfsmith.com.usgcac.txcdn.net' (in 'usgcac.txcdn.NET'?): 121.52.215.6#53
27-Aug-2009 01:18:23.374 lame server resolving 'images.golfsmith.com.usgcac.txcdn.net' (in 'usgcac.txcdn.NET'?): 121.52.215.6#53
27-Aug-2009 01:18:23.426 lame server resolving 'images.golfsmith.com.usgcac.txcdn.net' (in 'usgcac.txcdn.NET'?): 58.63.244.114#53



这个提示是正常的吗?

llzqq

没见过这些信息，GOOGLE上有很大讨论：

http://www.google.com/search?hl= ... r=&aq=f&oq=

bedreaming

原帖由 unix3er 于 2009-8-27 17:14 发表
谢谢两位,

使用 named -4后,果然没有 unreachable 这个提示.

但是多出来如下的提示(以前没有这个提示)

27-Aug-2009 00:58:49.799 lame server resolving 'images.golfsmith.com.usgcac.txcdn.net' (in ...

这个应该不是你的DNS服务器的问题，如果不想看到这样的日志，在named.conf的logging中用加入下面这个语句：
category lame-servers { null; };