[CentOS] Bind data directory borked on update from 5.3 to 5.4
Les Mikesell
lesmikesell at gmail.comTue Jan 19 23:47:37 UTC 2010
- Previous message: [CentOS] Bind data directory borked on update from 5.3 to 5.4
- Next message: [CentOS] Bind data directory borked on update from 5.3 to 5.4
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 1/19/2010 5:26 PM, Brian Mathis wrote: > On Tue, Jan 19, 2010 at 3:51 PM, Bowie Bailey<Bowie_Bailey at buc.com> wrote: >> I updated my secondary DNS server from 5.3 to 5.4 today. After the >> update, named would not start. A bit of investigation found that all of >> the files in /var/named/chroot/var/named/data had been turned into links >> to themselves! >> >> Fortunately, since this is a secondary DNS, all I had to do was delete >> the files, replace the root hints file and let everything else copy back >> over from the master. If this had been the master, I would have had to >> restore from backups. >> >> Has anyone else seen this problem? >> >> -- >> Bowie > > > Do you have the caching-nameserver package installed? I've heard this > can cause problems with files getting overwritten. If you install the caching-nameserver package it assumes you don't have any other configuration (that's that point of it being a caching-nameserver). -- Les Mikesell lesmikesell at gmail.com
- Previous message: [CentOS] Bind data directory borked on update from 5.3 to 5.4
- Next message: [CentOS] Bind data directory borked on update from 5.3 to 5.4
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the CentOS mailing list