b10-loadzone problem bind10-devel-20120517

Spain, Dr. Jeffry A. spainj at countryday.net
Tue May 22 11:23:45 UTC 2012


I understand that with the Sqlite data source, b10-loadzone is able to load zone files in relative as well as in full canonical format. This has been working for me with various forward DNS zone files, but it fails on our reverse zone file as shown below. The domain 128/26.156.203.74.in-addr.arpa has been delegated to us by our ISP. When I load this zone data in relative format, the names of all of the PTR records are the zone origin and the relative names in the zone file are interpreted to be the TTLs. This is despite a $TTL directive in the second line of the file. When I load the zone data in canonical format, it appears to be correct.

Jeffry A. Spain
Network Administrator
Cincinnati Country Day School

--------------------

root at precise:~# cat 128-26.156.203.74.in-addr.arpa-rel.db 
$ORIGIN .
$TTL 3600       ; 1 hour
128/26.156.203.74.in-addr.arpa IN SOA ns1.jaspain.net. hostmaster.jaspain.net. (
                                2012052201 ; serial
                                86400      ; refresh (1 day)
                                3600       ; retry (1 hour)
                                1209600    ; expire (2 weeks)
                                3600       ; minimum (1 hour)
                                )
                        NS      ns1.jaspain.net.
                        NS      ns2.jaspain.net.
$ORIGIN 128/26.156.203.74.in-addr.arpa.
128                     PTR     jas-74-203-156-128.jaspain.net.
129                     PTR     jas-74-203-156-129.jaspain.net.
130                     PTR     jas-74-203-156-130.jaspain.net.
131                     PTR     jas-74-203-156-131.jaspain.net.
root at precise:~# b10-loadzone 128-26.156.203.74.in-addr.arpa-rel.db
Using SQLite3 database file /var/bind10-devel/zone.sqlite3
Zone name is 128/26.156.203.74.in-addr.arpa.
Loading file "128-26.156.203.74.in-addr.arpa-rel.db"
8 RR(s) loaded in 0.10 second(s) (100.00% of 128-26.156.203.74.in-addr.arpa-rel.db)
Done.
root at precise:~# dig @localhost 128/26.156.203.74.in-addr.arpa axfr

; <<>> DiG 9.9.1 <<>> @localhost 128/26.156.203.74.in-addr.arpa axfr
; (1 server found)
;; global options: +cmd
128/26.156.203.74.in-addr.arpa. 3600 IN SOA     ns1.jaspain.net. hostmaster.jaspain.net. 2012052201 86400 3600 1209600 3600
128/26.156.203.74.in-addr.arpa. 3600 IN NS      ns1.jaspain.net.
128/26.156.203.74.in-addr.arpa. 3600 IN NS      ns2.jaspain.net.
128/26.156.203.74.in-addr.arpa. 128 IN  PTR     jas-74-203-156-128.jaspain.net.
128/26.156.203.74.in-addr.arpa. 129 IN  PTR     jas-74-203-156-129.jaspain.net.
128/26.156.203.74.in-addr.arpa. 130 IN  PTR     jas-74-203-156-130.jaspain.net.
128/26.156.203.74.in-addr.arpa. 131 IN  PTR     jas-74-203-156-131.jaspain.net.
128/26.156.203.74.in-addr.arpa. 3600 IN SOA     ns1.jaspain.net. hostmaster.jaspain.net. 2012052201 86400 3600 1209600 3600
;; Query time: 7 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue May 22 06:51:46 2012
;; XFR size: 8 records (messages 1, bytes 310)

--------------------

root at precise:~# cat 128-26.156.203.74.in-addr.arpa-full.db            
128/26.156.203.74.in-addr.arpa.               3600 IN SOA       ns1.jaspain.net. hostmaster.jaspain.net. 2012052201 86400 3600 1209600 3600
128/26.156.203.74.in-addr.arpa.               3600 IN NS        ns1.jaspain.net.
128/26.156.203.74.in-addr.arpa.               3600 IN NS        ns2.jaspain.net.
128.128/26.156.203.74.in-addr.arpa.           3600 IN PTR       jas-74-203-156-128.jaspain.net.
129.128/26.156.203.74.in-addr.arpa.           3600 IN PTR       jas-74-203-156-129.jaspain.net.
130.128/26.156.203.74.in-addr.arpa.           3600 IN PTR       jas-74-203-156-130.jaspain.net.
131.128/26.156.203.74.in-addr.arpa.           3600 IN PTR       jas-74-203-156-131.jaspain.net.
root at precise:~# b10-loadzone 128-26.156.203.74.in-addr.arpa-full.db
Using SQLite3 database file /var/bind10-devel/zone.sqlite3
Zone name is 128/26.156.203.74.in-addr.arpa.
Loading file "128-26.156.203.74.in-addr.arpa-full.db"
8 RR(s) loaded in 0.05 second(s) (100.00% of 128-26.156.203.74.in-addr.arpa-full.db)
Done.
root at precise:~# dig @localhost 128/26.156.203.74.in-addr.arpa axfr 

; <<>> DiG 9.9.1 <<>> @localhost 128/26.156.203.74.in-addr.arpa axfr
; (1 server found)
;; global options: +cmd
128/26.156.203.74.in-addr.arpa. 3600 IN SOA     ns1.jaspain.net. hostmaster.jaspain.net. 2012052201 86400 3600 1209600 3600
128/26.156.203.74.in-addr.arpa. 3600 IN NS      ns1.jaspain.net.
128/26.156.203.74.in-addr.arpa. 3600 IN NS      ns2.jaspain.net.
128.128/26.156.203.74.in-addr.arpa. 3600 IN PTR jas-74-203-156-128.jaspain.net.
129.128/26.156.203.74.in-addr.arpa. 3600 IN PTR jas-74-203-156-129.jaspain.net.
130.128/26.156.203.74.in-addr.arpa. 3600 IN PTR jas-74-203-156-130.jaspain.net.
131.128/26.156.203.74.in-addr.arpa. 3600 IN PTR jas-74-203-156-131.jaspain.net.
128/26.156.203.74.in-addr.arpa. 3600 IN SOA     ns1.jaspain.net. hostmaster.jaspain.net. 2012052201 86400 3600 1209600 3600
;; Query time: 4 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue May 22 06:52:15 2012
;; XFR size: 8 records (messages 1, bytes 326)



More information about the bind10-users mailing list