upgrading from bind4 to 9.2.1

[Pete Ehlke]

On Mon, Aug 05, 2002 at 04:43:26PM +0200, Tichahleyi Mpofu wrote:
> 
> Hie
> 
> Having upgraded from to bind 9 i encounter the following problems
> 
> ./named -c /etc/named.conf -g
> Aug 05 15:20:10.858 starting BIND 9.2.1 -c /etc/named.conf -g
> Aug 05 15:20:10.865 using 1 CPU
> ug 05 15:20:12.076 /etc/named.conf:672: zone 'abc.co.zw': already exists
> Aug 05 15:20:12.109 /etc/named.conf:1482: zone 'cab.co.zw': already exists
> Aug 05 15:20:12.119 /etc/named.conf:1627: zone 'nsa.co.zw': already exists
> Aug 05 15:20:12.124 /etc/named.conf:1632: zone 'xxx.co.zw': already exists
> Aug 05 15:20:12.819 loading configuration: failure
> Aug 05 15:20:12.824 exiting (due to fatal error)
> 
> Any clues
> 
Yes. Stop posting the same message over and over and over again. And you
have abc.co.zw, cab.co.zw, nsa.co.zw, and xxx.co.zw (are those the real
names?) defined more than once in named.conf. This was tolerated in
older versions, but not in newer ones.

Since you're running BIND 9, you should learn to use named-checkconf and
named-checkzone. There is no excuse for BIND logging configuration
errors on startup.

-P.