CODEWITHSUNDEEP
dnsbind9
Development FlazHost
Development FlazHost

Reputation: 329

Reverse DNS Server Can't Find NXDOMAIN Bind9

I'm setting up DNS with Bind9, but I couldn't resolve the reverse DNS.

This is my named.conf.local file:

zone "alice-abm.id"  { type master; file "/etc/bind/db.alice-abm.id"; };
zone "190.193.116.in-addr.arpa" { type master; file "/etc/bind/db.190.193.116.in-addr.arpa"; };

This is my db.alice-abm.id file:

;
; BIND data file for local loopback interface
;
$TTL    604800
@       IN      SOA     alice-abm.id. admin.alice-abm.id. (
                        2021112801      ; Serial
                         604800         ; Refresh
                          86400         ; Retry
                        2419200         ; Expire
                         604800 )       ; Negative Cache TTL
;
@       IN      NS      ns1.alice-abm.id.
@       IN      NS      ns2.alice-abm.id.
@       IN      A       116.193.190.67
ns1     IN      A       116.193.190.67
ns2     IN      A       116.193.190.67
www     IN      CNAME   @ ;Bisa juga dengan alice-abm.id

And this is my db.190.193.116.in-addr.arpa file:

;
; BIND data file for local loopback interface
;
$TTL    604800
@       IN      SOA     alice-abm.id. admin.alice-abm.id. (
                        20211128003     ; Serial
                         604800         ; Refresh
                          86400         ; Retry
                        2419200         ; Expire
                         604800 )       ; Negative Cache TTL
;
$ORIGIN 190.193.116.in-addr.arpa.
@       IN      NS      ns1.alice-abm.id.
@       IN      NS      ns2.alice-abm.id.
@       IN      A       116.193.190.67
67      IN      PTR     alice-abm.id.

When I try to nslookup the IP Address:

$ nslookup 116.193.190.67

That's return errors:

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

Is there any mistake I did?

Pleas help, and thanks.

Upvotes: 0

Views: 4375

Answers (1)

Bob Goddard
Bob Goddard

Reputation: 977

I would look at your logs, but the serial number is supposed to be unsigned 32bit, and 20211128003 far exceeds it. I think you mean 2021112803. The zone is probably not getting loaded.

Unless you have full control of that /24, I would make the zone 67.190.193.116.in-addr.arpa

Upvotes: 0

Related Questions