Reverse Lookup problem

[Mark_Andrews at isc.org]

> Hello Everyone, 
> Can anyone  tell  me if there is a problem with th revers lookup. The OS is
> Redhat 7.02. The  reverse lookup does not work for any IP address except
> 127.0.0.1.
> 
> dig -x 192.168.33.19    - --  returns error
> Returns error so as nslookup
> Thanks
> ----------------------------------------------------------------------------
> ------------------filename: 0.168.192.in-addr.arpa.zone----------------------
> ----
> 
> $ORIGIN 33.168.192.in-addr.arpa
> $TTL 86400
> @       IN      SOA     unidns1.mydom.com.  root.mydom.com. (
>                         3 ; serial
>                         28800 ; refresh
>                         7200 ; retry
>                         604800 ; expire
>                         86400 ; ttl
>                         );
> 
>         IN      NS      unidns1.mydom.com.
> 
> 19      IN      PTR     unidns1.mydom.com.
> 165     IN      PTR     ptree.mydim.com.
> 
> --------------------unidns1.mydom.zone-------------------------------------
> mydom.zone
> $TTL 86400
> @       IN      SOA     unidns1.mydom.com.  root.mydom.com. (
>                         3 ; serial
>                         28800 ; refresh
>                         7200 ; retry
>                         604800 ; expire
>                         86400 ; ttl
>                         );
> @       IN      NS unidns1
> @       IN      NS unidns1.mydom.com.
> @       IN      A 127.0.0.1
> @       IN      A       192.168.33.19
> unidns1 IN      A       192.168.33.19
> ptree   IN      A       192.168.33.165
> ----------------------------------------------------------------------------
> ------------------------------- /etc/named.conf------------------------------
> -----------------
> ## named.conf - configuration for bind
> #
> # Generated automatically by bindconf, alchemist et al.
> 
> controls {
>         inet  127.0.0.1 allow  { localhost; } keys { rndckey; };
> };
> 
> #include "/etc/rndc.key";
> 
> 
> options {
>         directory "/var/named/";
>         allow-query { any; };
>         allow-transfer { any; };
>         auth-nxdomain yes;
> };
> 
> 
> logging {
>      channel syslogd {
>          syslog local0;
>      };
>          channel logfile {
>          file "/var/named/named.log";
>          print-time yes;
>          };
>         category config { syslogd; };
>      };
> #
> 
> zone  "." {
>         type hint;
>         file  "named.ca";
> };
> 
> zone  "mydom.com" {
>         type master;
>         file  "mydom.com.zone";
> };
> 
> zone "33.168.192.in-addr.arpa"  {
>         type master;
>         file "0.168.192.in-addr.arpa.zone";
>         allow-update { none; };
> };
> zone "0.0.127.in-addr.arpa" {
>         type master;
>         file "localhost.zone";
> };
> 
> -------------------- Messages Log -------------------------------------
> .
> The only thing in message/log file with respect to the arpa is:
> 
> Sep 24 19:10:19 unidns1 named[2035]: dns_master_load:
> 0.168.192.in-addr.arpa.zon
> e:11: 33.168.192.in-addr.arpa.33.168.192.in-addr.arpa: not at top of zone
> Sep 24 19:10:19 unidns1 named[2035]: dns_zone_load: zone
> 33.168.192.in-addr.arpa
> /IN: loading master file 0.168.192.in-addr.arpa.zone: not at top of zone
> Sep 24 19:10:19 unidns1 named[2035]: running
> 
 
	Your $ORIGIN's are not absolute.  Also they are not necessary
	at all as the default $ORIGIN is the name of the zone.
	Nameservers have lots of features most of which are not
	needed for simple configurations.

	I would still make the name of the file match the
	name of the zone.

	Are you sure you want mydom.com to have an address of
	127.0.0.1 in addition to 192.168.33.19?  Replace the "@"
	with "localhost" and move down one line to keep all the
	records at the top of zone together.

	You have duplicate NS records for mydom.com.

	Mark
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at isc.org