; <<>> DiG 9.7.1-P2 <<>> -x 192.168.0.200
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5796
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;200.0.168.192.in-addr.arpa.    IN    PTR

;; ANSWER SECTION:
200.0.168.192.in-addr.arpa. 172800 IN    PTR    piter.casa.com.

;; AUTHORITY SECTION:
0.168.192.in-addr.arpa.    172800    IN    NS    200.168.192.in-addr.arpa.

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Jan 25 18:51:22 2011
;; MSG SIZE  rcvd: 90

спасибо большое вам но по моему поличилось может я ошибаюсь

Jan 25 17:22:40 piter named[15647]: zone 0.168.192.in-addr.arpa/IN: NS '200.0.168.192.in-addr.arpa' has no address records (A or AAAA)
Jan 25 17:22:40 piter named[15647]: zone 0.168.192.in-addr.arpa/IN: not loaded due to errors.

проверяйте синтаксис написания зоны.

; <<>> DiG 9.7.1-P2 <<>> -x 127.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41455
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 2

;; QUESTION SECTION:
;1.0.0.127.in-addr.arpa.        IN    PTR

;; ANSWER SECTION:
1.0.0.127.in-addr.arpa.    604800    IN    PTR    localhost.

;; AUTHORITY SECTION:
0.0.127.in-addr.arpa.    604800    IN    NS    localhost.

;; ADDITIONAL SECTION:
localhost.        604800    IN    A    127.0.0.1
localhost.        604800    IN    AAAA    ::1

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Jan 25 18:24:22 2011
;; MSG SIZE  rcvd: 121

dig -x 127.0.0.1

и покажите результат

cat /etc/named.conf
# Copyright (c) 2001-2004 SuSE Linux AG, Nuernberg, Germany.
# All rights reserved.
#
# Author: Frank Bodammer, Lars Mueller <lmuelle@suse.de>
#
# /etc/named.conf
#
# This is a sample configuration file for the name server BIND 9.  It works as
# a caching only name server without modification.
#
# A sample configuration for setting up your own domain can be found in
# /usr/share/doc/packages/bind/sample-config.
#
# A description of all available options can be found in
# /usr/share/doc/packages/bind/misc/options.

options {

    # The directory statement defines the name server's working directory

    directory "/var/lib/named";

    # Write dump and statistics file to the log subdirectory.  The
    # pathenames are relative to the chroot jail.

    dump-file "/var/log/named_dump.db";
    statistics-file "/var/log/named.stats";

    # The forwarders record contains a list of servers to which queries
    # should be forwarded.  Enable this line and modify the IP address to
    # your provider's name server.  Up to three servers may be listed.

    #forwarders { 192.0.2.1; 192.0.2.2; };

    # Enable the next entry to prefer usage of the name server declared in
    # the forwarders section.

    #forward first;

    # The listen-on record contains a list of local network interfaces to
    # listen on.  Optionally the port can be specified.  Default is to
    # listen on all interfaces found on your system.  The default port is
    # 53.

    #listen-on port 53 { 127.0.0.1; };

    # The listen-on-v6 record enables or disables listening on IPv6
    # interfaces.  Allowed values are 'any' and 'none' or a list of
    # addresses.

    listen-on-v6 { any; };

    # The next three statements may be needed if a firewall stands between
    # the local server and the internet.

    #query-source address * port 53;
    #transfer-source * port 53;
    #notify-source * port 53;

    # The allow-query record contains a list of networks or IP addresses
    # to accept and deny queries from. The default is to allow queries
    # from all hosts.

    #allow-query { 127.0.0.1; };

    # If notify is set to yes (default), notify messages are sent to other
    # name servers when the the zone data is changed.  Instead of setting
    # a global 'notify' statement in the 'options' section, a separate
    # 'notify' can be added to each zone definition.

    notify no;

    disable-empty-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";
    include "/etc/named.d/forwarders.conf";
};

# To configure named's logging remove the leading '#' characters of the
# following examples.
#logging {
#    # Log queries to a file limited to a size of 100 MB.
#    channel query_logging {
#        file "/var/log/named_querylog"
#            versions 3 size 100M;
#        print-time yes;            // timestamp log entries
#    };
#    category queries {
#        query_logging;
#    };
#
#    # Or log this kind alternatively to syslog.
#    channel syslog_queries {
#        syslog user;
#        severity info;
#    };
#    category queries { syslog_queries; };
#
#    # Log general name server errors to syslog.
#    channel syslog_errors {
#        syslog user;
#        severity error;
#    };
#    category default { syslog_errors;  };
#
#    # Don't log lame server messages.
#    category lame-servers { null; };
#};

# The following zone definitions don't need any modification.  The first one
# is the definition of the root name servers.  The second one defines
# localhost while the third defines the reverse lookup for localhost.

zone "." in {
    type hint;
    file "root.hint";
};

zone "localhost" in {
    type master;
    file "localhost.zone";
};

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

# Include the meta include file generated by createNamedConfInclude.  This
# includes all files as configured in NAMED_CONF_INCLUDE_FILES from
# /etc/sysconfig/named

include "/etc/named.conf.include";
zone "casa.com" in {
    allow-transfer { any; };
    file "master/casa.comXX";
    type master;
};
zone "0.168.192.in-addr.arpa" in {
    allow-transfer { any; };
    file "master/0.168.192.in-addr.arpaXX";
    type master;
};
logging {
    category default { log_syslog; };
    channel log_syslog { syslog; };
};

# You can insert further zone records for your own domains below or create
# single files in /etc/named.d/ and add the file names to
# NAMED_CONF_INCLUDE_FILES.
# See /usr/share/doc/packages/bind/README.SUSE for more details

ещё покажите конфиг:

; <<>> DiG 9.7.1-P2 <<>> -x piter.casa.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 46906
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;com.casa.piter.in-addr.arpa.    IN    PTR

;; AUTHORITY SECTION:
in-addr.arpa.        10361    IN    SOA    A.ROOT-SERVERS.NET. dns-ops.ARIN.NET. 2011012504 1800 900 691200 10800

;; Query time: 33 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Jan 25 17:28:55 2011
;; MSG SIZE  rcvd: 112

dig  piter.casa.com

; <<>> DiG 9.7.1-P2 <<>> piter.casa.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25468
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;piter.casa.com.            IN    A

;; ANSWER SECTION:
piter.casa.com.        172800    IN    A    192.168.0.200

;; AUTHORITY SECTION:
casa.com.        172800    IN    NS    piter.casa.com.

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Jan 25 17:30:36 2011
;; MSG SIZE  rcvd: 62

; <<>> DiG 9.7.1-P2 <<>> -x 192.168.0.200
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 12515
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;200.0.168.192.in-addr.arpa.    IN    PTR

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Jan 25 17:24:38 2011
;; MSG SIZE  rcvd: 44

я заменил ip на 192.168.0.200

Опишите пожалуйста детальнее проблему. Вы настраиваете DNS на локальной машине и посылаете запрос на возврат обратной зоны локального компьютера?

nslookup
> piter.casa.com
Server:        127.0.0.1
Address:    127.0.0.1#53

Name:    piter.casa.com
Address: 192.168.0.200
> 192.168.0.200
;; Got SERVFAIL reply from 127.0.0.1, trying next server
;; Got SERVFAIL reply from 192.168.0.200, trying next server
;; Got SERVFAIL reply from 127.0.0.1, trying next server
;; Got SERVFAIL reply from 192.168.0.200, trying next server
Server:        212.73.32.3
Address:    212.73.32.3#53

** server can't find 200.0.168.192.in-addr.arpa.: NXDOMAIN