bind 9.1.3rc2 has been failed

[James A Griffin]

Piotr Kasztelowicz wrote:
[snip]
> I have this corrected. Now in messages is:
> 
> Jun 29 10:36:50 sun su: 'su root' succeeded for pekasz on /dev/pts/2
> Jun 29 10:37:33 sun /usr/local/sbin/named[23430]: starting BIND 9.1.3rc2
> Jun 29 10:37:33 sun /usr/local/sbin/named[23430]: using 1 CPU
> Jun 29 10:37:33 sun /usr/local/sbin/named[23430]: loading configuration
> from '/etc/named.conf'
> Jun 29 10:37:33 sun /usr/local/sbin/named[23430]: the default for the
> 'auth-nxdomain' option is no
> w 'no'
This is just a notice to tell you about a change in the default.

> Jun 29 10:37:33 sun /usr/local/sbin/named[23430]: no IPv6 interfaces found
> Jun 29 10:37:33 sun /usr/local/sbin/named[23430]: listening on IPv4
> interface lo0, 127.0.0.1#53
> Jun 29 10:37:33 sun /usr/local/sbin/named[23430]: listening on IPv4
> interface hme0, 212.51.193.152
> #53
> Jun 29 10:37:33 sun /usr/local/sbin/named[23430]: unknown logging category
> 'parser' ignored
> Jun 29 10:37:33 sun /usr/local/sbin/named[23430]: unknown logging category
> 'db' ignored
> Jun 29 10:37:33 sun /usr/local/sbin/named[23430]: unknown logging category
> 'eventlib' ignored
> Jun 29 10:37:33 sun /usr/local/sbin/named[23430]: unknown logging category
> 'packet' ignored
> Jun 29 10:37:33 sun /usr/local/sbin/named[23430]: unknown logging category
> 'cname' ignored
> Jun 29 10:37:33 sun /usr/local/sbin/named[23430]: unknown logging category
> 'os' ignored
> Jun 29 10:37:33 sun /usr/local/sbin/named[23430]: unknown logging category
> 'insist' ignored
> Jun 29 10:37:33 sun /usr/local/sbin/named[23430]: unknown logging category
> 'maintenance' ignored
> Jun 29 10:37:33 sun /usr/local/sbin/named[23430]: unknown logging category
> 'load' ignored
> Jun 29 10:37:33 sun /usr/local/sbin/named[23430]: unknown logging category
> 'response-checks' ignor
> ed

You have 'category' phrases in your named.conf for categories that are
not valid.  You can find the list of valid categories in section
6.2.10.2 of ~/doc/arm/Bv9ARM.ch06.html.

> 
> and in /var/tmp/named.run is
> 
> Jun 29 10:37:33.945 general: dns_zone_load: zone katowice.ptkardio.pl/IN:
> loading zone: no master
> file configured: continuing

Since you did not post your complete named.conf, I am not sure, but I
think the the katowice.ptkardio.pl zone is a slave.  If so, then you
need to add the phrase 'master { ip-address; };' 

For example:

zone "athena.inc"{
        type slave;
        file "sec/athena.inc";
        masters{
                192.168.1.8;
        };
        notify no;
        allow-transfer{
                none;
        };
        allow-query{
                192.168.1.0/24;
        };
        allow-update{
                none;
        };

> Jun 29 10:37:33.978 general: dns_master_load: lodz.ptkardio:1: no TTL
> specified
> Jun 29 10:37:33.980 general: dns_zone_load: zone lodz.ptkardio.pl/IN:
> loading master file lodz.ptk
> ardio: no ttl

Every RR need a time-to-live value.  It can be specified in each RR or a
default can be specified by using the $TTL directive at the top of (1st
line) the zone file (database).  Just add a line like '$TTL 86400      ;
1 day'.  Pick a value appropriate to your needs.

> Jun 29 10:37:33.981 general: running
> Jun 29 10:37:48.985 general: refresh_callback: zone
> katowice.ptkardio.pl/IN: failure for 213.227.1
> 00.13#53: timed out
> Jun 29 10:37:49.201 xfer-in: transfer of 'katowice.ptkardio.pl' from
> 213.227.100.13#53: end of tra
> nsfer
> 
> I don't known if this is already correct - at nslookup by bind9
> I can't list the domain and at bind8 al ist OK and nslookup
> anwers.

Correct your named.conf and add the $TTL to the zone files.  You should
learn to use 'dig' rather than use 'nslookup' when you test your
servers.  What was the 'nslookup' failure message?
> 
> At bind9 this is said "running" but the sentence that zone loaded
> with serial is not written to named.run, therefor I have
> neverless to go back to bind8.
> 
Regards,
Jim