I could use some help.

I have finally NAMED starting again after hours of research but now I have two problems. One is errors in named.run that I'm not sure how to correct(listed next) and the other is bizarre. The bizarre one is that older entries in a zone work up to a point and new entries in a zone work. However, entries created at a certain point in time do not work. All entries show up in eDirectory under the zone and contain the same attributes. I'm really at a loss as to how some would work and others not. Especially, with new entries working. This is OES2SP2 with latest patches. Also NAMED seems to be reading eDir correctly.

I am not sure what information to provide on the second problem so just let me know if you need more details and I'll post them. Thanks for any help.

named.run(edited.)
25-Jun-2010 10:47:12.051 general: main: notice: starting BIND 9.3.2 -u

(Normal zone startup lines - named with return code: 0)

25-Jun-2010 10:47:13.163 general: dns/db: info: Unable to get attribute [DNS_dnsdhcpifolder.dnsdhcpifolder] list, attribute doesn't exists.

(Other zones look fine.)

25-Jun-2010 10:47:13.185 general: dns/zone: error: zone RootServerInfo/IN: has no NS records
25-Jun-2010 10:47:13.185 general: dns/zone: error: zone RootServerInfo/IN: zone is not loaded bad zone
25-Jun-2010 10:47:13.185 general: server: notice: running

Named.conf

options {
forwarders {192.168.1.5;192.168.1.6;};
novell_zone-list {"bob.joebob.com.dnsdhcpifolder";"184_18_172_IN-ADDR_ARPA.dnsdhcpifolder";"1_168_192_IN-ADDR_ARPA.dnsdhcpifolder";"RootServerInfo.dnsdhcpi folder";};
novell_server-dnsname "bob.joebob.com";
novell_server-mod-time 1277476864;
novell_server-dn "DNS_dnsdhcpifolder.dnsdhcpifolder";
};
zone "bob.joebob.com." IN {
file "bob.joebob.com.db";

type master;
novell_zone-servers {"DNS_dnsdhcpifolder.dnsdhcpifolder";};
novell_designated-server "DNS_dnsdhcpifolder.dnsdhcpifolder";
check-names ignore;

novell_zone-mod-time 1277475987;
novell_zone-creation-time 1277342614;
novell_zone-dn "bob_joebob_com.dnsdhcpifolder";
};
zone "184.18.172.IN-ADDR.ARPA." IN {
file "184.18.172.IN-ADDR.ARPA.db";

type master;
novell_zone-servers {"DNS_dnsdhcpifolder.dnsdhcpifolder";};
novell_designated-server "DNS_dnsdhcpifolder.dnsdhcpifolder";
check-names ignore;

novell_zone-mod-time 1277475987;
novell_zone-creation-time 1277342929;
novell_zone-dn "184_18_172_IN-ADDR_ARPA.dnsdhcpifolder";
};
zone "1.168.192.IN-ADDR.ARPA." IN {
file "1.168.192.IN-ADDR.ARPA.db";

type master;
novell_zone-servers {"DNS_dnsdhcpifolder.dnsdhcpifolder";};
novell_designated-server "DNS_dnsdhcpifolder.dnsdhcpifolder";
check-names ignore;

novell_zone-mod-time 1277475987;
novell_zone-creation-time 1277343013;
novell_zone-dn "1_168_192_IN-ADDR_ARPA.dnsdhcpifolder";
};
zone "RootServerInfo." IN {
file "RootServerInfo.db";

type master;
novell_zone-servers {"DNS_dnsdhcpifolder.dnsdhcpifolder";};
novell_designated-server "DNS_dnsdhcpifolder.dnsdhcpifolder";
forwarders {192.168.1.5;192.168.1.6;};
novell_zone-mod-time 1277477202;
novell_zone-creation-time 1277474565;
novell_zone-dn "RootServerInfo.dnsdhcpifolder";
};