LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   rDNS Config Problem - not found: 3(NXDOMAIN) (https://www.linuxquestions.org/questions/linux-newbie-8/rdns-config-problem-not-found-3-nxdomain-4175457244/)

mouthpiec 04-07-2013 11:33 AM

rDNS Config Problem - not found: 3(NXDOMAIN)
 
Hi,
I use this forum several times to troubleshoot my problems and usually from old posts I manage to find my solution ... but this time I have to post this question although it seems relatively easy. :rolleyes:

I am using a BIND DNS installed on a CentOS V6 and I am trying to configure Reverse DNS (normal DNS is working fine).

Details of my problem below:

Server IP Config
Code:

[root@testserver named]# ifconfig | grep "inet addr"
          inet addr:172.16.243.16  Bcast:172.16.243.255  Mask:255.255.255.0
          inet addr:127.0.0.1  Mask:255.0.0.0

Hostname
Code:

[root@testserver]# hostname
testserver.intra

Error I am getting
Code:

[root@testserver named]# host 172.16.243.16
Host 16.243.16.172.in-addr.arpa. not found: 3(NXDOMAIN)

Config in named.conf
Code:

[root@testserver named]# more /etc/named.conf
//
// named.conf
//
// Provided by Red Hat bind 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.
//

options {
        listen-on port 53 { 127.0.0.1; };
        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";
        allow-query    { localhost; };
        recursion yes;

        dnssec-enable yes;
        dnssec-validation yes;
        dnssec-lookaside auto;

        /* Path to ISC DLV key */
        bindkeys-file "/etc/named.iscdlv.key";

        managed-keys-directory "/var/named/dynamic";
};

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

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

zone "open-ims.test" IN {
        type master;
        file "open-ims.dnszone";
        allow-transfer { none; };
        allow-update { 127.0.0.1; };
};

// zone "0.0.127.in-addr.arpa" {
//        type master;
//        file "0.0.127.in-addr.arpa";
// };

zone "243.16.172.in-addr.arpa" {
      type master;
      file "243.16.172.in-addr.arpa";
};

include "/etc/named.rfc1912.zones";
include "/etc/named.root.key";

Config in Reverse DNS Zone File
Code:

[root@testserver named]# more 243.16.172.in-addr.arpa
@              IN      SOA    testserver.intra.      root.testserver.intra. (
                        2013000016 ; serial
                        1H ; refresh
                        15M ; retry
                        14D ; expire
                        12H ; default_ttl
                        )
@              IN      NS      testserver.intra.
16              IN      PTR    testserver.intra.


Hope the above is enough to help you help me :)
thanks in advance!

bathory 04-07-2013 02:31 PM

Hi and welcome to LQ,

The 243.16.172.in-addr.arpa zone file looks good.
Are you sure you've increased the serial after editing it. What gives:
Code:

named-checkconf -z

mouthpiec 04-07-2013 04:09 PM

thanks for the reply!

result here:
Code:

zone open-ims.test/IN: loaded serial 2006101001
243.16.172.in-addr.arpa:1: no TTL specified; using SOA MINTTL instead
zone 243.16.172.in-addr.arpa/IN: loaded serial 2013000018
zone localhost.localdomain/IN: loaded serial 0
zone localhost/IN: loaded serial 0
zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: loaded serial 0
zone 1.0.0.127.in-addr.arpa/IN: loaded serial 0
zone 0.in-addr.arpa/IN: loaded serial 0

also it seems that by changing the serial the change is being noted by the process:
Code:

243.16.172.in-addr.arpa:1: no TTL specified; using SOA MINTTL instead
zone 243.16.172.in-addr.arpa/IN: loaded serial 2013000016
zone 0.in-addr.arpa/IN: loaded serial 0
zone 1.0.0.127.in-addr.arpa/IN: loaded serial 0
243.16.172.in-addr.arpa:1: no TTL specified; using SOA MINTTL instead
zone 243.16.172.in-addr.arpa/IN: loaded serial 2013000017
zone 0.in-addr.arpa/IN: loaded serial 0
zone 1.0.0.127.in-addr.arpa/IN: loaded serial 0
243.16.172.in-addr.arpa:1: no TTL specified; using SOA MINTTL instead
zone 243.16.172.in-addr.arpa/IN: loaded serial 2013000018


mouthpiec 04-07-2013 04:20 PM

added TTL to remove that warning. Warning removed but IP not being resolved

Code:

zone open-ims.test/IN: loaded serial 2006101001
zone 243.16.172.in-addr.arpa/IN: loaded serial 2013000019
zone localhost.localdomain/IN: loaded serial 0
zone localhost/IN: loaded serial 0
zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: loaded serial 0
zone 1.0.0.127.in-addr.arpa/IN: loaded serial 0
zone 0.in-addr.arpa/IN: loaded serial 0


Code:

# host 172.16.243.16
Host 16.243.16.172.in-addr.arpa. not found: 3(NXDOMAIN)


mouthpiec 04-07-2013 05:21 PM

hi again ... issue was solved :D

I had to configure it as a DNS server for my machine by modifying /etc/resolv.conf file

Code:

vi /etc/resolv.conf
nameserver 127.0.0.1
search open-ims.test
domain open-ims.test

Still cannot understand the reason behind this but issue was solved.

Thanks!


All times are GMT -5. The time now is 07:10 AM.