logo       
Google Custom Search
    AddThis Social Bookmark Button
-->

[BUG] BIND 9.2.2rc1 refuses to load valid (and self-generated) zonefile: msg#00456

Subject: [BUG] BIND 9.2.2rc1 refuses to load valid (and self-generated) zonefile
Hi.

I set up the TLD "NAMED." for testing purposes. My primary master is on
192.168.0.43, and I have a slave on 192.168.0.114. I have a working zone
with a couple of A and NS records in it. Then I ran the following in
nsupdate:
------------
server 192.168.0.43
zone NAMED.
update add * 300 IN NS ns01.foo.com.

^D
------------
The result now is that I get the following entry in my zonefile
(cut'n'paste from a zonetransfer):
$ORIGIN named.
@                       1D IN SOA       ns01.nic hostmaster.nic (
                                        2002082803      ; serial
                                        8H              ; refresh
                                        2H              ; retry
                                        1W              ; expiry
                                        1D )            ; minimum

                        1D IN NS        ns01.nic
*                       5M IN NS        ns01.foo.com.
...

This is fine, and doing a query on a domain that is not listed in the
zonefile for "NAMED." works as expected:

$ dig @192.168.0.43 oijaoijd.oijadoiajd.named. ns
; <<>> DiG 8.3 <<>> @192.168.0.43 oijaoijd.oijadoiajd.named. ns
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUERY SECTION:
;;      oijaoijd.oijadoiajd.named, type = NS, class = IN

;; AUTHORITY SECTION:
oijaoijd.oijadoiajd.named.  5M IN NS  ns01.foo.com.

;; Total query time: 1 msec
;; FROM: test.np to SERVER: 192.168.0.43
;; WHEN: Wed Aug 28 15:14:15 2002
;; MSG SIZE  sent: 43  rcvd: 69

This works fine when querying the slave as well.

I then stop named with rndc stop. When I now run named-checkzone, I get:
# /usr/local/bind/sbin/named-checkzone named.
/usr/local/bind/var/named.zone dns_master_load: 
/usr/local/bind/var/named.zone:13: *.named: invalid NS owner name (wildcard)
zone named/IN: loading master file /usr/local/bind/var/named.zone: invalid NS 
owner name (wildcard)

Here's the relevant section from the zonefile, line numbers prepended:
11:$ORIGIN named.
12:$TTL 300     ; 5 minutes
13:*                    NS      ns01.foo.com.

When I start named, it refuses to give any replies to queries in the
"NAMED." zone, I'm assuming because it thinks the zone is invalid. That's
odd, because it seems to work perfectly fine before I stopped named! Also,
I can't find anything in the RFCs saying that (multiple) NS records for a
wildcard is not legal. Should this check be there at all? (I say multiple
because I've tested that as well, and it works fine until I try to start
named again).

Ketil





<Prev in Thread] Current Thread [Next in Thread>