[SOLVED] bind reverse zone; no name with reverse lookup

deadeyes · 10-12-2009, 08:39 AM

Hi all,

I am using RHEL5.

These are my config files:

Code:

options {
        listen-on port 53 { 127.0.0.1; 192.168.14.54; };
        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     { localhost; 192.168.0.0/16; };
};

key "rndckey" {
        algorithm hmac-md5;
        secret "hc+CTxxanRbhILf3yjvLeA==";
};

controls {
        inet 127.0.0.1 port 953
        allow { 127.0.0.1; } keys { "rndckey"; };
};

logging {
        channel default_debug {
                file "data/named.run";
                severity dynamic;
        };
};

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

        zone "mydomain.com" IN {
                type master;
                file "mydomain.com.zone";
        };
        zone "14.168.192.in-addr.arpa" IN {
                type master;
                file "mydomain.com.rev.zone";
                allow-update { none; };
        };
};

view localnet_resolver {
        match-clients      { 192.168.0.0/16; };
        match-destinations { 192.168.0.0/16; };
        recursion yes;
        include "/etc/named.rfc1912.zones";
        
        zone "mydomain.com" IN {
                type master;
                file "mydomain.com.zone";
        };

        zone "14.168.192.in-addr.arpa" IN {
                type master;
                file "mydomain.com.rev.zone";
                allow-update { none; };
        };
};

mydomain.com.zone is:

Code:

$TTL 4D
@       IN SOA mydomain.com. root.mydomain.com. (
                                        200910122
                                        16H
                                        4H
                                        2W
                                        4D
)

        IN NS names.mydomain.com.
        IN MX 10 names.mydomain.com.

names   IN A 192.168.14.54
ftp     IN CNAME names
www     IN CNAME names

And mydomain.com.rev.zone:

Code:

$TTL    86400
14.168.192.in-addr.arpa.       IN      SOA     mydomain.com. root.mydomain.com.  (
                                      2009101204 ; Serial
                                      28800      ; Refresh
                                      14400      ; Retry
                                      3600000    ; Expire
                                      86400 )    ; Minimum
@        IN      NS      names.mydomain.com.
54      IN      PTR     names.mydomain.com.
55      IN      PTR     www.mydomain.com.

In /var/log/messages I see no errors.
Forward lookup does work,
however reverse lookup does not work.

Code:

[root@mydomain named]# dig @192.168.14.54 192.168.14.55

; <<>> DiG 9.3.4-P1 <<>> @192.168.14.54 192.168.14.55
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 48869
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;192.168.14.55.                 IN      A

;; AUTHORITY SECTION:
.                       10388   IN      SOA     A.ROOT-SERVERS.NET. NSTLD.VERISIGN-GRS.COM. 2009101200 1800 900 604800 86400

;; Query time: 19 msec
;; SERVER: 192.168.14.54#53(192.168.14.54)
;; WHEN: Mon Oct 12 14:38:50 2009
;; MSG SIZE  rcvd: 106

I now have no clue what is wrong.

Anyone sees what I did wrong?

zhjim · 10-12-2009, 09:10 AM

As far as I can see you did not do any reverse lookup...
Use dig -x ip.add.re.ss to do a reverse lookup

I did not check on the config files cause DNS is of my mind for to long to remember most of the config options.

deadeyes · 10-12-2009, 09:21 AM

Quote:

Originally Posted by zhjim

As far as I can see you did not do any reverse lookup...
Use dig -x ip.add.re.ss to do a reverse lookup

I did not check on the config files cause DNS is of my mind for to long to remember most of the config options.

Code:

[root@mydomain dovecot]# dig @192.168.14.54 -x 192.168.14.55

; <<>> DiG 9.3.4-P1 <<>> @192.168.14.54 -x 192.168.14.55
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45949
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1

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

;; ANSWER SECTION:
55.14.168.192.in-addr.arpa. 86400 IN    PTR     www.mydomain.com.

;; AUTHORITY SECTION:
14.168.192.in-addr.arpa. 86400  IN      NS      names.mydomain.com.

;; ADDITIONAL SECTION:
names.mydomain.com.     345600  IN      A       192.168.14.54

;; Query time: 1 msec
;; SERVER: 192.168.14.54#53(192.168.14.54)
;; WHEN: Mon Oct 12 15:23:16 2009
;; MSG SIZE  rcvd: 110

Seems that it was working all along :s

Great! Thanks for your help!

zhjim · 10-12-2009, 10:54 AM

Jup the -x option to dig helped it