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