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