hey list, maybe offtopic, but bind8-update-relevant for me: during updating my 6.1-system, rpm told me to install bindutil before updating to bind8-8.2.3-0. there is no bindutil on my old rpm-cd's and so i downloaded the bindutil-update from the suse-server. during checking the installation of bindutil with rpm, i was told that there are a lot of conflicts with my old, non-binutil-using bind8.1.x.x. now what is the most elegant way of updating? uninstall the old bind8.1.x.x (saving conf's etc) or forcing the rpm- command? thanks in advance and sorry for wasting security-related-bandwidth...;-) daniel
hey list,
maybe offtopic, but bind8-update-relevant for me:
during updating my 6.1-system, rpm told me to install bindutil before updating to bind8-8.2.3-0. there is no bindutil on my old rpm-cd's and so i downloaded the bindutil-update from the suse-server. during checking the installation of bindutil with rpm, i was told that there are a lot of conflicts with my old, non-binutil-using bind8.1.x.x. now what is the most elegant way of updating? uninstall the old bind8.1.x.x (saving conf's etc) or forcing the rpm- command?
thanks in advance and sorry for wasting security-related-bandwidth...;-)
Not at all wasted. The package was split into bindutil and bind8. The best would be to deinstall bind8 and then to install the new bind8 and bindutil packages. Save the config files before, like cd / tar cfvv /root/nameserver.tar etc/named.conf var/named rpm -e bind8 # while the nameserver is running... doesn't matter. rpm -Uhv bind8.rpm # may be necessary to force these commands rpm -ihv bindutil.rpm # using --force and --nodeps and finally tar xfvvp /root/nameserver.tar and `rcnamed restart´ to make the changes effective.
daniel
Thanks,
Roman.
--
- -
| Roman Drahtmüller
Hello, On Thu, 1 Feb 2001, Roman Drahtmueller wrote:
during checking the installation of bindutil with rpm, i was told that there are a lot of conflicts with my old, non-binutil-using bind8.1.x.x. now what is the most elegant way of updating? uninstall the old bind8.1.x.x (saving conf's etc) or forcing the rpm- command?
cd / tar cfvv /root/nameserver.tar etc/named.conf var/named
rpm -e bind8 # while the nameserver is running... doesn't matter. rpm -Uhv bind8.rpm # may be necessary to force these commands rpm -ihv bindutil.rpm # using --force and --nodeps
and finally
tar xfvvp /root/nameserver.tar
and `rcnamed restart´ to make the changes effective.
And maybe (like Daniel and me have to do) edit your master zonefiles. This bind8 package seems to be restricter in syntax-checking. After changing the first two lines in each zonefile from: @ IN SOA ns.example.org. hostmaster.example.org. ( to: $TTL 1D @ IN SOA ns.example.org. hostmaster.example.org. ( (the "(" has to be in the SOA line) bind accepted my zonefiles without errors.
daniel
Thanks, Roman.
cheers Michael -- Michael Röhrkasten http://www.behrensoft.de Fingerprint: D4F5 5F01 4EDA 8F4F ED81 1EFE 0D63 E06C CD64 FB5E
Hi Roman, Roman Drahtmueller wrote:
Save the config files before, like
cd / tar cfvv /root/nameserver.tar etc/named.conf var/named
rpm -e bind8 # while the nameserver is running... doesn't matter. rpm -Uhv bind8.rpm # may be necessary to force these commands rpm -ihv bindutil.rpm # using --force and --nodeps
and finally
tar xfvvp /root/nameserver.tar
and `rcnamed restart´ to make the changes effective.
After the update I got some messages like Feb 1 11:51:37 xyz named[8058]: zone: 19.172.in-addr.arpa/IN: non-glue record at bottom of zone: 254.78.19.172.in-addr.arpa/PTR in /var/log/messages. What should I do to eliminate this? Another effect was that nslookup didn't found any host. Increasing the serial number of the SOA record and reloading named solved this problem. andy -- ------------------------------- mailto:Andreas.Tirok@beusen.de fon: +49 30 549932-37 fax: +49 30 549932-21
participants (4)
-
Andreas Tirok -
Daniel Quappe -
Muckl -
Roman Drahtmueller