my reverse lookup is not working from another network.
 

I have configured my DNS in Centos5, every thing is working fine, bt whenever i try to nslookup reverse than,the reply will be
***ns1.abc.net.np cant find 202.38.7.217:non-existent domain bt the forward lookup works perfectly. But at he same time reverse lookup works perfectly from our pool of ip address.

In my named.conf file evry thing is fine, here is my conf file..


//
// named.caching-nameserver.conf
//
// Provided by Red Hat caching-nameserver package to configure the
// ISC BIND named(8) DNS server as a caching only nameserver
// (as a localhost DNS resolver only).
//
// See /usr/share/doc/bind*/sample/ for example named configuration files.
//
// DO NOT EDIT THIS FILE - use system-config-bind or an editor
// to create named.conf - edits to this file will be lost on
// caching-nameserver package upgrade.
//
options {
listen-on port 53 {127.0.0.1; 202.38.7.219; };
# forwarders {8.8.8.8; 165.21.83.88; };
listen-on-v6 port 53 { ::1; };
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
memstatistics-file "/var/named/data/named_mem_stats.txt";

// Those options should be used carefully because they disable port
// randomization
// query-source port 53;
// query-source-v6 port 53;

allow-query { any;};
allow-query-cache { any; };
};
logging {
channel default_debug {
file "data/named.run";
severity dynamic;
};

channel named_file
{
file "/var/log/named.log" versions 99 size 10m;
print-time yes;
print-category yes;
print-severity yes;
};

channel log_requests
{
file "/var/log/queries.log" versions 99 size 30m;
print-time yes;
print-category yes;
print-severity yes;
};

category queries
{
log_requests;
};

category default
{
named_file;
};

};

view localhost_resolver {
match-clients { any; };
match-destinations { any; };
recursion yes;
include "/etc/named.rfc1912.zones";
};

file named.rfc1912.zones


[root@ns1 chroot]# cat /etc/named.rfc1912.zones
// named.rfc1912.zones:
//
// Provided by Red Hat caching-nameserver package
//
// ISC BIND named zone configuration for zones recommended by
// RFC 1912 section 4.1 : localhost TLDs and address zones
//
// See /usr/share/doc/bind*/sample/ for example named configuration files.
//
zone "." IN {
type hint;
file "named.ca";
};

zone "airwave.net.np" IN {
type master;
file "airwave.net.np.zone";
allow-transfer { yy.yy.yy.yy; yy.yy.yy.yy; };
allow-update { none; };
};

#zone "airwave.com.np" IN {
# type master;
# file "airwave.com.np.zone";
# allow-transfer { yy.yy.yy.yy; yy.yy.yy.yy; };
# allow-update { none; };
#};

zone "7.38.202.in-addr.arpa" IN {
type master;
file "reverse.myreversefile";
allow-transfer { yy.yy.yy.yy; yy.yy.yy.yy; };
allow-update { none; };
};

Please reply...Due to this problem some of my mail bounch...

Are you sure you have control over the PTR record of your IP?

It's your ISP that should set up the PTR record

java socket

yes I am sure..I set up the PTR record.

As you see from the above dig output, your dns refuses the query for the reverse zone (the same goes for the forward zone)
So, I guess you need to remove or comment out the view localhost_resolver, so your dns starts acting as an authoritative dns

Regards

Thankx,
Bt the view locahost_resolver is already comment out..

It is not:

Thankx a lot for your concern. The problem has been solved.The main issue is from the APENIC. The configuration was fine but the reverse lookup was not updated from the APENIC. That is the reason why the lookup was refused through the internet. :)
Thankx again