Setting up caching-only server on BIND 9.2?

[Kevin Darcy]

AJ Fisher wrote:

>I am trying to configure DNS caching-only server for an HP-UX 11.00 server
>with BIND 9.20.
>
>Here is the content of the following files:
>
>named.conf:
>
># Name: named.conf
>
>options {
>
>directory "/etc";
>
>};
>
>#
>
># Local Domains
>
>#
>
>zone "0.0.127.in-addr.arpa" {
>
>type master;
>
>file "db.127.0.0";
>
>};
>
>#
>
># Cache Records
>
>#
>
>zone "." {
>
>type hint;
>
>file "db.cache";
>
>};
>
>#
>
>db.127.0.0:
>
>; ;=========================================================================
>
>; Name: /etc/db.127.0.0
>
>;=========================================================================
>
>;
>
>;
>
>; DOMAIN: 0.0.127.in-addr.arpa.
>
>;
>
>0.0.127.in-addr.arpa. IN SOA hedgehog.ca.boeing.com. (
>
>96021700 ; Serial /*day versions*/
>
>7200 ; Refresh /*2 hrs*/
>
>900 ; Retry /*15 minutes*/
>
>864000 ; Expire /*10 days*/
>
>999999999) ; Minimum TTL /*infinite*/
>
>;
>
>0.0.127.in-addr.arpa. IN NS hedgehog.ca.boeing.com.
>
>;
>
>1.0.0.127.in-addr.arpa. IN PTR localhost.
>
>; ;=========================================================================
>
>; Name: db.cache
>
>;=========================================================================
>
>;
>
>;
>
>. 99999999 IN NS venus.boeing.com.
>
>99999999 IN NS hera.boeing.com.
>
>99999999 IN NS hermes.boeing.com.
>
>99999999 IN NS jupiter.boeing.com.
>
>;
>
>;
>
>venus.boeing.com. 99999999 IN A xxx.42.5.51
>
>hera.boeing.com. 99999999 IN A xxx.52.1.11
>
>hermes.boeing.com. 99999999 IN A xxx.240.5.11
>
>jupiter.boeing.com. 99999999 IN A xxx.203.5.11
>
>;
>
>(I have xed out the first octet on purpose for this e-mail)
>
>Here is the output from the syslog.log file for named:
>
>Jan 13 17:26:58 hedgehog named [4116]: starting BIND 9.2.0
>
>Jan 13 17:26:58 hedgehog named [4116]: using 1 CPU
>
>Jan 13 17:26:58 hedgehog named [4116]: loading configuration from
>'/etc/named.conf'
>
>Jan 13 17:26:58 hedgehog named [4116]: no IPv6 interfaces found
>
>Jan 13 17:26:58 hedgehog named [4116]: listening on IPv4 interface lan0,
>130.42.107.71#53 Jan 13 17:26:58 hedgehog named[4116]: listening on IPv4
>interface lo0, 127.0.0.1#53
>
>Jan 13 17:26:58 hedgehog named[4116]: none:0: open: /etc/rndc.key: file not
>found
>
>Jan 13 17:26:58 hedgehog named [4116]: couldn't add command channel
>127.0.0.1#953: file not found
>
>Jan 13 17:26:58 hedgehog named [4116]: no source of entropy found
>
>Jan 13 17:26:58 hedgehog named [4116]: dns_rdata_fromtext: db.127.0.0:19:
>near eol: unexpected end of input
>
>Jan 13 17:26:58 hedgehog named [4116]: zone 0.0.127.in-addr.arpa/IN: loading
>master file db.127.0.0:
>
>Jan 13 17:26:58 hedgehog named [4116]: running
>
>
>
>Here is the error message I get when I do an nslookup:
>
>*** Can't find server name for address 127.0.0.1: Server failed
>
>I don't have rndc.key set up. I am also wondering why I am seeing
>"unexpected end of input" messages in the syslog.log file. Any help or
>insight you can provide would be greatly appreciated!
>
The "unexpected end of input" messages are symptomatic of the 
0.0.127.in-addr.arpa zone being rejected, which in turn explains why 
nslookup is barfing (better lookup tools like "dig", by the way, don't 
do this ridiculous "do a reverse lookup of the server being queried" 
nonsense, so they don't barf in situations like this). The reason the 
zone is being rejected is because your SOA record has too few fields in 
it (it's missing the RNAME field). You should probably put a $TTL 
directive at the top of the zone file too.

                                                                         
                        - Kevin