named.conf errors

Hello to all

I'd like to find out the most common reasons of the following error:

cannot redefine zone 'somedomain.com' class INcannot redefine zone 'somedomain.com' class IN

I've checked the TTL settings and they are configured fine

$TTL 3600

/etc/named.conf relevant line :

zone "somedomain.com" {type master;file "primaries/somedomain.com.zone";};

Sample Zone file attached

Maybe it's some duplicate entries error .

Any thoughts ...
Thanks

I'll need to see an unedited named.conf please. And I need to know what version of BIND you're using.

Hello

You are right, i'm missing some important information .
Bind version 8.2.4 on SunOS 5.8 platform .
About the named.conf ... it's too sensitive to publish .
I can add only edited parts of it . Options part is added here:

options {
version "Microsoft DNS Server SP 6.0";
query-source address xxx.xxx.xxx.xx;
directory "/var/named";
also-notify {xxx.xxx.xxx.xx;xxx.xxx.xxx.xx;xxx.xxx.xxx.xxx;127.0.0.1;};
allow-transfer {xxx.xxx.xxx.xx;xxx.xxx.xxx.xx;xxx.xxx.xxx.xxx;127.0.0.1;};
allow-recursion {AllowedRecursive;};
blackhole {Unwanted;};
listen-on {Me;};
transfer-source xxx.xxx.xxx.xx;
transfer-format many-answers;
transfers-in 20;
}

This named.conf file is 8421 lines light ... you don't want to see it all - trust me
The problem occurs on several domains .
Thank you for any kind of help or search direction

The error does mean that a zone has been defined more than once, and this is invalid. Here's some things to remember:

1) you cannot define a master and a slave for a zone on the same server
2) All zones are NOT case sensitive. So you will get that error if you add "FreeWilly.com" and "freewilly.com" to the same named.conf file.
3) Watch out for included files which may have zones defined in the parent. This is one way to accidentally add a zone twice.
4) There was a bug in earlier versions of BIND before 8.2.2 where you'd get that error. So it there's some likelihood the bug still exists in some form. An upgrade to BIND 9.2.3 is recommended.
5) One way to test your configuration for duplicate zones is to remove the offending zone from the named.conf. Then reload the configuration and see if the zone still exists on the server.

Thanks for the points.

Actually I know them and it was checked before the post to this forum. The reason of solving the errors is upgrade to new 9.2.3 version - I'd like to start the upgrade with "clean" and perfect configuration .
Do you think that only upgrade can solve the errors of this kind?
Can I count on it ?

Thanks for your time

It's not guaranteed. I'm more interested in seeing the results of the test as laid out in step 5. If the zone still exists after you remove the zone (and there's no longer an error), then it's a case of duplicate zones. If the zone does not exist after you remove the zone (and there's no longer an error), then it's a case of a buggy version. If you continue to get the error, then remove the zone again at the new line position it gives you.

Thanks .

I'm checking

Best regards