DNS不能正常解析,万分火急！！！

sunliguo008 · 发表于 2009-4-1 16:02:35

大家好，前些天刚刚做的DNS,一直能够正常使用，但是这周上班我发现DNS不可用了，查资料弄了好久还是不能解析域名，问题：DNS不能进行解析，在服务器上可解析。使用ip可解析.在其他机器上不能解析。
希望大家能帮我解决一下，我把部分配置文件贴出来：
//
// Sample named.conf BIND DNS server 'named' configuration file
// for the Red Hat BIND distribution.
//
// See the BIND Administrator's Reference Manual (ARM) for details, in:
// file:///usr/share/doc/bind-*/arm/Bv9ARM.html
// Also see the BIND Configuration GUI : /usr/bin/system-config-bind and
// its manual.
//
options
{
      /* make named use port 53 for the source of all queries, to allow
      * firewalls to block all ports except 53:
      */
      query-source port 53;
      query-source-v6 port 53;

      // Put files that named is allowed to write in the data/ directory:
      directory "/var/named"; // the default
      dump-file             "data/cache_dump.db";
      statistics-file       "data/named_stats.txt";
      memstatistics-file    "data/named_mem_stats.txt";

};
logging
{
/*    If you want to enable debugging, eg. using the 'rndc trace' command,
*    named will try to write the 'named.run' file in the $directory (/var/named).
*    By default, SELinux policy does not allow named to modify the /var/named directory,
*    so put the default debug log file in data/ :
*/
      channel default_debug {
            file "data/named.run";
            severity dynamic;
      };
};
//
// All BIND 9 zones are in a "view", which allow different zones to be served
// to different types of client addresses, and for options to be set for groups
// of zones.
//
// By default, if named.conf contains no "view" clauses, all zones are in the
// "default" view, which matches all clients.
//
// If named.conf contains any "view" clause, then all zones MUST be in a view;
// so it is recommended to start off using views to avoid having to restructure
// your configuration files in the future.
//
view "localhost_resolver"
{
/* This view sets up named to be a localhost resolver ( caching only nameserver ).
* If all you want is a caching-only nameserver, then you need only define this view:
*/
      match-clients          { localhost; };
      match-destinations    { localhost; };
      recursion yes;
      # all views must contain the root hints zone:
      include "/etc/named.root.hints";

      /* these are zones that contain definitions for all the localhost
      * names and addresses, as recommended in RFC1912 - these names should
      * ONLY be served to localhost clients:
      */
      zone "dlrtvu.bt"{
         type master;
         file "dlrtvu.bt.db";
         allow-transfer{none;};
      };

      zone "229.47.210.in-addr.arpa" IN {
         type master;
         file "dlrtvu.bt.db.arpa";
         allow-transfer{none;};
      };
      include "/etc/named.rfc1912.zones";
};
view "internal"
{
/* This view will contain zones you want to serve only to "internal" clients
that connect via your directly attached LAN interfaces - "localnets" .
*/
      match-clients          { localnets; };
      match-destinations    { localnets; };
      recursion yes;
      // all views must contain the root hints zone:
      include "/etc/named.root.hints";

      // include "named.rfc1912.zones";
      // you should not serve your rfc1912 names to non-localhost clients.

      // These are your "authoritative" internal zones, and would probably
      // also be included in the "localhost_resolver" view above :

      zone "dlrtvu.bt" {
            type master;
            file "dlrtvu.bt.db";
            allow-transfer{none;};
      };
      zone "229.47.210.in-addr.arpa" IN {
            type master;
            file "dlrtvu.bt.db.arpa";
            allow-transfer{none;};
      };
      zone "my.slave.internal.zone" {
            type slave;
            file "slaves/my.slave.internal.zone.db";
            masters { 210.47.229.90 ;} ;
            // put slave zones in the slaves/ directory so named can update them
      };
      zone "my.ddns.internal.zone" {
            type master;
            allow-update { key ddns_key; };
            file "slaves/my.ddns.internal.zone.db";
            // put dynamically updateable zones in the slaves/ directory so named can update them
      };
};
key ddns_key
{
      algorithm hmac-md5;
      secret "gi0BwiwSrHwJObkXzUWwq4qGLnhBsv6AiB8qnJ8pDgZBNgq6hAqkOr6QvOLc";
};
view "external"
{
/* This view will contain zones you want to serve only to "external" clients
* that have addresses that are not on your directly attached LAN interface subnets:
*/
      match-clients          { !localnets; !localhost; };
      match-destinations    { !localnets; !localhost; };

      recursion no;
      // you'd probably want to deny recursion to external clients, so you don't
      // end up providing free DNS service to all takers

      // all views must contain the root hints zone:
      include "/etc/named.root.hints";

      // These are your "authoritative" external zones, and would probably
      // contain entries for just your web and mail servers:

      zone "my.external.zone" {
            type master;
            file "my.external.zone.db";
      };
};

正向解析文件：
[root@dbserver named]# cat dlrtvu.bt.db
$TTL 38400
@ in soa dlrtvu.bt. root 2009040101 3H 15M 1W 1D
   IN NS dns.dlrtvu.bt.
dns IN A 210.47.229.90
www IN A 210.47.229.7
ftp IN A 210.47.229.241
反向解析文件：
$TTL 38400
@ in soa dns.dlrtvu.bt. root 2009040101 3H 15M 1W 1D
   IN NS dns.dlrtvu.bt.
90 IN PTR dns.dlrtvu.bt.
7  IN PTR www.dlrtvu.bt.
241 IN PTR ftp.dlrtvu.bt.

=============================================================

Apr  1 15:11:05 dbserver named[2083]: shutting down: flushing changes
Apr  1 15:11:05 dbserver named[2083]: stopping command channel on 127.0.0.1#953
Apr  1 15:11:05 dbserver named[2083]: stopping command channel on ::1#953
Apr  1 15:11:05 dbserver named[2083]: no longer listening on 127.0.0.1#53
Apr  1 15:11:05 dbserver named[2083]: no longer listening on 210.47.229.90#53
Apr  1 15:11:05 dbserver named[2083]: exiting
Apr  1 15:11:07 dbserver named[3916]: starting BIND 9.3.3rc2 -u named -t /var/named/chroot
Apr  1 15:11:07 dbserver named[3916]: found 2 CPUs, using 2 worker threads
Apr  1 15:11:07 dbserver named[3916]: loading configuration from '/etc/named.conf'
Apr  1 15:11:07 dbserver named[3916]: listening on IPv4 interface lo, 127.0.0.1#53
Apr  1 15:11:07 dbserver named[3916]: listening on IPv4 interface eth0, 210.47.229.90#53
Apr  1 15:11:07 dbserver named[3916]: command channel listening on 127.0.0.1#953
Apr  1 15:11:07 dbserver named[3916]: command channel listening on ::1#953
Apr  1 15:11:07 dbserver named[3916]: zone 0.in-addr.arpa/IN/localhost_resolver: loaded serial 42
Apr  1 15:11:07 dbserver named[3916]: zone 0.0.127.in-addr.arpa/IN/localhost_resolver: loaded serial 1997022700
Apr  1 15:11:07 dbserver named[3916]: zone 229.47.210.in-addr.arpa/IN/localhost_resolver: loaded serial 2009040101
Apr  1 15:11:07 dbserver named[3916]: zone 255.in-addr.arpa/IN/localhost_resolver: loaded serial 42
Apr  1 15:11:07 dbserver named[3916]: zone 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/localhost_resolver: loaded serial 1997022700
Apr  1 15:11:07 dbserver named[3916]: zone dlrtvu.bt/IN/localhost_resolver: loaded serial 2009040101
Apr  1 15:11:07 dbserver named[3916]: zone localdomain/IN/localhost_resolver: loaded serial 42
Apr  1 15:11:07 dbserver named[3916]: zone localhost/IN/localhost_resolver: loaded serial 42
Apr  1 15:11:07 dbserver named[3916]: zone 229.47.210.in-addr.arpa/IN/internal: loaded serial 2009040101
Apr  1 15:11:07 dbserver named[3916]: zone dlrtvu.bt/IN/internal: loaded serial 2009040101
Apr  1 15:11:07 dbserver named[3916]: slaves/my.ddns.internal.zone.db:1: no TTL specified; using SOA MINTTL instead
Apr  1 15:11:07 dbserver named[3916]: zone my.ddns.internal.zone/IN/internal: loaded serial 1
Apr  1 15:11:07 dbserver named[3916]: slaves/my.slave.internal.zone.db:1: no TTL specified; using SOA MINTTL instead
Apr  1 15:11:07 dbserver named[3916]: zone my.slave.internal.zone/IN/internal: loaded serial 1
Apr  1 15:11:07 dbserver named[3916]: my.external.zone.db:1: no TTL specified; using SOA MINTTL instead
Apr  1 15:11:07 dbserver named[3916]: zone my.external.zone/IN/external: loaded serial 1
Apr  1 15:11:07 dbserver named[3916]: running
Apr  1 15:11:07 dbserver named[3916]: zone my.slave.internal.zone/IN/internal: expired
Apr  1 15:11:07 dbserver named[3916]: zone my.slave.internal.zone/IN/internal: refresh: non-authoritative answer from master 210.47.229.90#53 (source 0.0.0.0#0)
Apr  1 15:11:07 dbserver named[3916]: zone dlrtvu.bt/IN/localhost_resolver: sending notifies (serial 2009040101)
Apr  1 15:11:07 dbserver named[3916]: zone dlrtvu.bt/IN/internal: sending notifies (serial 2009040101)
Apr  1 15:11:07 dbserver named[3916]: client 210.47.229.90#1030: view localhost_resolver: received notify for zone 'dlrtvu.bt'
Apr  1 15:11:07 dbserver named[3916]: client 210.47.229.90#1030: view localhost_resolver: received notify for zone 'dlrtvu.bt'
Apr  1 15:12:06 dbserver named[3916]: zone my.slave.internal.zone/IN/internal: refresh: non-authoritative answer from master 210.47.229.90#53 (source 0.0.0.0#0)
Apr  1 15:13:40 dbserver named[3916]: zone my.slave.internal.zone/IN/internal: refresh: non-authoritative answer from master 210.47.229.90#53 (source 0.0.0.0#0)
Apr  1 15:17:13 dbserver named[3916]: zone my.slave.internal.zone/IN/internal: refresh: non-authoritative answer from master 210.47.229.90#53 (source 0.0.0.0#0)
Apr  1 15:23:57 dbserver named[3916]: zone my.slave.internal.zone/IN/internal: refresh: non-authoritative answer from master 210.47.229.90#53 (source 0.0.0.0#0)
Apr  1 15:36:16 dbserver named[3916]: zone my.slave.internal.zone/IN/internal: refresh: non-authoritative answer from master 210.47.229.90#53 (source 0.0.0.0#0)

提示Apr  1 15:36:16 dbserver named[3916]: zone my.slave.internal.zone/IN/internal: refresh: non-authoritative answer from master 210.47.229.90#53 (source 0.0.0.0#0)

这样的日志，一直没能解决是怎么回事，希望网友们能帮忙解决一下，十分急急！！！

我的QQ:407137501

		自动登录	找回密码
密码			注册