[SOLVED] named not responding to queries

geek.ksa · 02-23-2010, 10:11 AM

Hi all,

My DNS server used to work flawlessly but for some reason it no longer responds to queries. It seems that named always queries internet root serves!!

e.g.:

Code:

[root@nismaster ~]# dig +trace nismaster.desertpenguin.com

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> +trace nismaster.desertpenguin.com
;; global options:  printcmd
.                       518288  IN      NS      F.ROOT-SERVERS.NET.
.                       518288  IN      NS      G.ROOT-SERVERS.NET.
.                       518288  IN      NS      H.ROOT-SERVERS.NET.
.                       518288  IN      NS      I.ROOT-SERVERS.NET.
.                       518288  IN      NS      J.ROOT-SERVERS.NET.
.                       518288  IN      NS      K.ROOT-SERVERS.NET.
.                       518288  IN      NS      L.ROOT-SERVERS.NET.
.                       518288  IN      NS      M.ROOT-SERVERS.NET.
.                       518288  IN      NS      A.ROOT-SERVERS.NET.
.                       518288  IN      NS      B.ROOT-SERVERS.NET.
.                       518288  IN      NS      C.ROOT-SERVERS.NET.
.                       518288  IN      NS      D.ROOT-SERVERS.NET.
.                       518288  IN      NS      E.ROOT-SERVERS.NET.
;; Received 500 bytes from 127.0.0.1#53(127.0.0.1) in 0 ms

com.                    172800  IN      NS      F.GTLD-SERVERS.NET.
com.                    172800  IN      NS      I.GTLD-SERVERS.NET.
com.                    172800  IN      NS      C.GTLD-SERVERS.NET.

.....

my domain zone file is as follows:

Code:

[root@nismaster ~]# cat /var/named/chroot/var/named/desertpenguin.com.zone
$TTL 4800
@       IN SOA  nismaster.desertpenguin.com. root.desertpenguin.com. (
                                50         ; serial
                                10800      ; refresh (3 hours)
                                900        ; retry (15 minutes)
                                604800     ; expire (1 week)
                                86400      ; minimum (1 day)
                                )
                       NS      nismaster
xyz                    A       192.168.1.1
nismaster              A       192.168.1.253
mail                   A       192.168.1.10

my named.conf file has:

Code:

[root@nismaster ~]# cat /var/named/chroot/etc/named.conf
options {
        #listen-on port 53 { 127.0.0.1; };
        listen-on port 53 { localhost; };
        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; };
        allow-query     { localnets; };
        #allow-query-cache { localhost; };
        allow-query-cache { localnets; };
        allow-transfer { localnets; };
};
logging {
        channel default_debug {
                file "data/named.run";
                severity dynamic;
        };
};
view localhost_resolver {
        match-clients      { localnets; };
        match-destinations { localhost; };
        recursion yes;
        zone "desertpenguin.com" IN {
        type master;
        file "desertpenguin.com.zone";
        allow-update { localnets; };
        forwarders {};
        };
        include "/etc/named.rfc1912.zones";
};

when I try to resolve one of the A records above:

Code:

[root@nismaster ~]# dig nismaster.desertpenguin.com

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> nismaster.desertpenguin.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 41237
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;nismaster.desertpenguin.com.   IN      A

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Feb 23 19:10:53 2010
;; MSG SIZE  rcvd: 45

Please, any hints?
Thanks in advance!

bathory · 02-23-2010, 05:42 PM

Hi,

Quote:

My DNS server used to work flawlessly but for some reason it no longer responds to queries. It seems that named always queries internet root serves!!

Runnig dig +trace, you query the root servers recursively, so this is normal.

You zone file looks good. Remove or comment out from named.conf the:

Quote:

forwarders {};
allow-query-cache { localnets; };

The 1st has no sense and the 2nd is useless for an authoritative name server. You can also do the same at least for

Quote:

match-destinations { localhost; };

There is no need to be so restrictive for an internal dns.

ilikejam · 02-23-2010, 05:45 PM

That's odd.

What does /etc/resolv.conf look like?

Dave

geek.ksa · 02-24-2010, 03:00 AM

@Bathory: Thanks for the good hints

@ilikejam: Oh yeah, it sure "was" odd, it drove me nuts!! it had nothing to do with the resolv.conf. In fact, the issue was that the DDNS journal file was out of sync with the zone file!!, deleting DDNS journal file resolved the issue instantly.

Thanks all.