Dear Michal, Thank you very much for your useful reply below. I was indeed aware that the RPMs were experimental, hence my jucidious use of a test server! :-)
Simply by copying named.conf as you suggested gets the server component working. The tools (dig etc) are used both manually and by a number of scripts. Following the upgrade without enabling SCL, dig (for example) was the previous version which came from the previous Copr package. Is there any official/recommended method for updating server to make the new tools the default? You also comented about using "--without scl" with SRPMs. Does this give the previous behaviour? Also, what is the correct location from which to download the SRPMs? With many thanks. Best wishes, Matthew ------ >From: Micha? K?pie? <mic...@isc.org> >To: Matthew Richardson <matthe...@itconsult.co.uk> >Cc: bind-users@lists.isc.org >Date: Thu, 9 May 2019 09:19:13 +0200 >Subject: Re: isc-bind-esv Repository - "yum update" doing undesirable things! >Hi Matthew, > >> I have been using the isc-bind-esv repository on Centos 7 since it was >> created. On each upgrade, a "yum update" has done the correct thing by >> upgrading from the running version to the latest version. >> >> Today (happily on a cloned test server!) I repeated this with the upgrade >> being from 9.11.6 to 9.11.6.P1-1.2.el7. >> >> It seems that the package names have changed and that Bind is now installed >> in a new directory structure below /opt/isc. In my case, a previously >> working authoratitive configuration is now comprehensively broken. >> >> Before troubleshooting, I was wondering whether I had missed any release >> notes or similar which might explain what is going on. > >First of all, thanks for trying these packages out and apologies for the >trouble caused. This is an intentional change in a repository which ISC >has always been describing as experimental [1]. > >A few months ago, we decided that Software Collections [2] are the >preferred long-term solution for our RPM packages. Among other things, >this was prompted by the package conflicts people were running into when >using our Coprs [3]. What you observed on your server is an update from >non-SCL packages to SCL packages. > >To make your previous setup work with SCL packages, please move your >/etc/named.conf to /opt/isc/isc-bind/root/etc/named.conf. If you >previously enabled named startup upon boot and you still want that to be >the case, please run: > > systemctl start isc-bind-named > >BIND utilities (e.g. dig, rndc) are available after enabling the >Software Collection, for example using: > > scl enable isc-bind bash > >This disruption was a one-off - we plan to soon move our Copr >repositories away from their current experimental status. Once that >happens, care will be taken not to break existing installations. > >Once again, apologies for the inconvenience. If you have any further >questions, please feel free to ask them. > >Hope this helps, > >[1] See https://www.isc.org/blogs/bind-9-packages/ and the description > of the Copr itself. > >[2] https://www.softwarecollections.org/ > >[3] https://lists.isc.org/pipermail/bind-users/2019-January/101277.html, > for example _______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
