BIND 9.2.1 - Reverse Lookup???

[tobyheywood]

My problem is a trivial one both one which is causing the loss of a large quantity of hair from on top of my head.

When I make a ssh connection to my primary RH9 server for sum reason it would appear as though reverse lookup isn't working as far as the login program is concerned and iptables is concerned. I am assuming it is reverse lookup as ssh hangs for about 30 seconds before displaying the ip instead of the dns returned name.

In order to try and get to the bottom of this I tried to ping numerous hosts (including the hostname of the localhost and it managed to retrieve the ip and return a ping. Next I tried the host command followed by the ip of the host in question and again everything came back as expected.

Below are copies of all files which I have created to get DNS working on my network. Can anyone see the (probably) obvious mistake which is causing me to lose hair over something so trivial.

cat /etc/resolv.conf

nameserver 0.0.0.0
search dfd.int

cat /etc/nsswitch.conf (only required line)

#hosts:     db files nisplus nis dns
hosts:      dns [!UNAVAIL=return] files

cat /etc/host.conf

order bind,hosts
multi on

cat /etc/named.conf

options {
        directory "/var/named";
        query-source address * port 53;
};

zone "." IN {
        type hint;
        file "named.ca";
};

zone "localhost" IN {
        type master;
        file "localhost.zone";
        allow-update { none; };
};

zone "0.0.127.in-addr.arpa" IN {
        type master;
        file "named.local";
        allow-update { none; };
};

zone "dfd.int" IN {
        type master;
        file "db.dfd.int";
        allow-update { none; };
};

zone "20.168.192.in-addr.arpa" IN {
        type master;
        file "20.168.192.in-addr.arpa";
        allow-update { none; };
};

/var/named/db.dfd.int:

$TTL 1w
@               SOA     barney.dfd.int. hostmaster.dfd.int. (
                        2004210301      ; serial
                        6h              ; Refresh
                        30m             ; Retry
                        7d              ; Expire
                        15m )           ; Negative Cache TTL
; Defining the nameservers
                NS      barney.dfd.int.
; Defining the mail servers
                MX      5 barney.dfd.int.
;
; Localhost
localhost       A       127.0.0.1
;
; Hosts
dap1            A       192.168.20.5
barney          A       192.168.20.10
pickles         A       192.168.20.80
ftp             CNAME   barney.dfd.int.
www             CNAME   barney.dfd.int.
smtp            CNAME   barney.dfd.int.
mail            CNAME   barney.dfd.int.
intranet        CNAME   barney.dfd.int.

cat /var/named/20.168.192.in-addr.arpa

$TTL 1w
@               SOA     barney.dfd.int. hostmaster.dfd.int. (
                        2004220301      ; Serial
                        6h              ; Refresh
                        30m             ; Retry
                        7d              ; Expire
                        15m )           ; Negative Cahce TTL
;
; Define name servers
                NS      barney.dfd.int.
;
; Hosts
5               PTR     dap1.dfd.int.
10              PTR     barney.dfd.int.
80              PTR     pickles.dfd.int.

I would be hugely greatfully if anyone can point out any errors which cause the problems I am experiencing. Or if you can confirm that everything looks to be fine I will then begin to investigate other avenues.

Having said all of the above i think I am going made as a last ditch attempt to test what is has failed. I stopped named altered both nsswitch.conf to look at the host file first and altered the host.conf to look at the hosts file first then logged out and tried again, again a space 30 seconds lapse occurs before the password pompt.

Sorry for the long explaination, HHHEEELLLPPP!!!!

Regards

Toby Heywood

 

[gui95]

Maybe :
#cat /etc/resolv.conf
nameserver 127.0.01
search dfd.int

regards,

GBy

 

[tobyheywood]

I've tried turning off the firewall which speeds things up a little but still it appears to be unable to resolve the name from the ip.

As I understood it, 0.0.0.0 and 127.0.0.1 basic mean the same thing. I tried it with 127.0.0.1 but still no joy.

Toby Heywood