caching-nameserver.noarch

General Discussion of atomic repo and development projects.

Ask for help here with anything else not covered by other forums.
faris
Long Time Forum Regular
Long Time Forum Regular
Posts: 2321
Joined: Thu Dec 09, 2004 11:19 am

caching-nameserver.noarch

Unread post by faris »

Can anyone enlighten me please?

I made the mistake or doing some updates on Cos4/Plesk the other night while half-asleep and without logging, and I'm wondering if I've done any damage.

Essentially I have removed caching-nameserver from a few of my personal VPSes. I *think* I did this because I saw errors like:

Code: Select all

  Updating  : caching-nameserver           ####################### [25/80]
/bin/mv: cannot move `/var/named/named.ca' to `/var/named/run-root/var/named/named.ca': No such file or directory
ln: `/var/named/named.ca': File exists
/bin/mv: cannot move `/var/named/named.local' to `/var/named/run-root/var/named/named.local': No such file or directory
ln: `/var/named/named.local': File exists
/bin/mv: cannot move `/var/named/named.ip6.local' to `/var/named/run-root/var/named/named.ip6.local': No such file or directory
ln: `/var/named/named.ip6.local': File exists
/bin/mv: cannot move `/var/named/named.broadcast' to `/var/named/run-root/var/named/named.broadcast': No such file or directory
ln: `/var/named/named.broadcast': File exists
/bin/mv: cannot move `/var/named/named.zero' to `/var/named/run-root/var/named/named.zero': No such file or directory
ln: `/var/named/named.zero': File exists
/bin/mv: cannot move `/var/named/localhost.zone' to `/var/named/run-root/var/named/localhost.zone': No such file or directory
ln: `/var/named/localhost.zone': File exists
/bin/mv: cannot move `/var/named/localdomain.zone' to `/var/named/run-root/var/named/localdomain.zone': No such file or directory
ln: `/var/named/localdomain.zone': File exists
error: %post(caching-nameserver-7.3-3.0.1.el4_6.noarch) scriptlet failed, exit status 1
When updating bind the other day.

No visible harm seems to have been done (I did backup named.conf before I removed caching-nameserver, and restored the conf file afterwards).

Bind is working. DNS is working. All seems to be working.

As I understand it, caching-namserver is basically a configuration change for bind that allows it to cache lookups it makes.

On a server I can see how this would be useful and reduce load when it comes to dnsrbl blacklists ... but nothing much else.

Anyway.... should I worry much about having removed this "package" (seems to be a script more than anything else)?

I can't seem to be able to restore it now that I've removed it. yum says there's no such package as caching-nameserver.

Faris.
--------------------------------
<advert>
If you want to rent a UK-based VPS that comes with friendly advice and support from a fellow ART fan, please get in touch.
</advert>
breun
Long Time Forum Regular
Long Time Forum Regular
Posts: 2813
Joined: Sat Aug 20, 2005 9:30 am
Location: The Netherlands

Unread post by breun »

Plesk recommends not installing caching-nameserver (nor bind-chroot which causes problems with Plesk): http://kb.parallels.com/en/234
Lemonbit Internet Dedicated Server Management
faris
Long Time Forum Regular
Long Time Forum Regular
Posts: 2321
Joined: Thu Dec 09, 2004 11:19 am

Unread post by faris »

Ah!

I knew bind-chroot was a no-no. I think in my half-sleep I confused bind-chroot with caching-namesever which is why I removed it. Maybe subconsiously I knew caching-nameserver was also a no-no, though to be honest I can't remember coming accross it before now.

Thanks for putting my mind at rest. Much appreciated.
--------------------------------
<advert>
If you want to rent a UK-based VPS that comes with friendly advice and support from a fellow ART fan, please get in touch.
</advert>
Post Reply