Thanks for the answers.
About the following answer in case the provisionning gives zones duplicates:
Run the configuration through named-checkconf if you are worried. It
will catch the duplicates before you run named.
Does exist a tool to automaticaly remove the duplicates in the configuration?
> To: hugo...@hotmail.com
> CC: bind-us...@isc.org
> From: ma...@isc.org
> Subject: Re: migration bind8/bind9: config problems.
> Date: Wed, 16 Feb 2011 07:56:30 +1100
>
>
> Firstly please get your mail client fixed. Turning comma's to "=2C"
> isn't needed and defeats the purpose of printed quotable which is
> to do the minimum changes to make the message transmitable via 7bit
> smtp so that the message is readable by old clients. Anything above
> that minimum is a bug.
>
> In message <col105-w610d1e1f6dce88a566c29fac...@phx.gbl>, hugo hugoo writes:
> >
> > Dear all,
> >
> > I am testing an upgrade from bind8 to bind9.
> > For this, I have installed bind9 in a server with the same configuration
> > files as present in the server running bind8.
> > When I start bind9, I have the following errors and the server do not sta
> > rt.
> >
> > Can you anyone answer the questions presnet in the log here aboive to help
> > me with my migration?
> >
> > Thanks in advance,
> >
> > Hugo,
> >
> > eb 15 13:13:10 dnsextcache001 named[17541]: starting BIND 9.6-ESV-R3 -c /et
> > c/bind/named.conf
> > Feb 15 13:13:10 dnsextcache001 named[17541]: built with '--prefix=/usr/lo
> > cal/bind-9.6-ESV-R3'
> > Feb 15 13:13:10 dnsextcache001 named[17541]: using up to 4096 sockets
> > Feb 15 13:13:10 dnsextcache001 named[17541]: loading configuration from '/e
> > tc/bind/named.conf'
> > Feb 15 13:13:10 dnsextcache001 named[17541]: /etc/bind/named.conf:17: optio
> > n 'fetch-glue' is obsolete
> >
> > ==> can I remove this from the configuration without any impact?
>
> Yes. It can be safely removed.
>
> > Feb 15 13:13:13 dnsextcache001 named[17541]: loading configuration: failure
> > Feb 15 13:13:13 dnsextcache001 named[17541]: exiting (due to fatal error)
> > Feb 15 13:13:13 dnsextcache001 named[17541]: /etc/bind/conf/named.zones.inc
> > :488832: zone 'thermote-vanhalst.com': already exists previous definition:
> > /etc/bind/conf/named.zones.inc:93105
> > Feb 15 13:13:13 dnsextcache001 named[17541]: /etc/bind/conf/named.zones.inc
> > :489192: zone 'villedewavre.be': already exists previous definition: /etc/b
> > ind/conf/named.zones.inc:104087
> > Feb 15 13:13:13 dnsextcache001 named[17541]: /etc/bind/conf/named.zones.inc
> > :489912: zone 'saval.be': already exists previous definition: /etc/bind/con
> > f/named.zones.inc:186169
> > Feb 15 13:13:13 dnsextcache001 named[17541]: /etc/bind/conf/named.zones.inc
> > :490816: zone 'dataminercube.com': already exists previous definition: /etc
> > /bind/conf/named.zones.inc:384171
> > Feb 15 13:13:13 dnsextcache001 named[17541]: /etc/bind/conf/named.zones.inc
> > :491735: zone 'cdmeerhout.be': already exists previous definition: /etc/bin
> > d/conf/named.zones.inc:179099
> > Feb 15 13:13:13 dnsextcache001 named[17541]: /etc/bind/conf/named.zones.inc
> > :491745: zone 'agroservices.be': already exists previous definition: /etc/b
> > ind/conf/named.zones.inc:291937
> > Feb 15 13:13:13 dnsextcache001 named[17541]: loading configuration: failure
> > Feb 15 13:13:13 dnsextcache001 named[17541]: exiting (due to fatal error)
> >
> > ==> I can remove the duplicates to allow bind9 to start (bind8 starts
> > even if duplicates present).
> >
> > BUT!!
> >
> > I would like to have for this point the same behaviour as bind8 as it is po
> > ssible that the provisioning in hte future introduces duplicates as it is t
> > he case in my present setup.
> >
> > Is this possible?
>
> No. Run the configuration through named-checkconf if you are worried. It
> will catch the duplicates before you run named.
>
> Mark
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
