SCIENTIFIC-LINUX-USERS Archives

July 2008

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: Bind updating problem in SL4.6 (Initialization of named.conf by YUM update)
From:
Samuel Halicke <[log in to unmask]>
Reply To:
Samuel Halicke <[log in to unmask]>
Date:
Fri, 18 Jul 2008 11:04:00 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (70 lines) 
On Jul 18, 2008, at 7:02 AM, Ichihara Takashi wrote:

> Hi
>
> After updating of bind of SL4.6 on 12th (11th) July by YUM,
> the previous configuration file /var/named/chroot/etc/named is
> renamed as named.conf.rpmsave, and a new initial configuration
> file is stored as /var/named/chroot/etc/named, at least on SL4.6
> X86_86 and SL46 i386 distributions. This seems to be opposite.!!
> As a result, several bind users seems to have encountered the
> problem by the initialization of the named.conf file.
>
> So, all the bind users of SL 4.6 are recommended to check the
> bind configuration files (/var/named/chroot/etc/named.conf)
> after updating by YUM on 12th ( or 11th) July 2008.
>
>>
>> =
>> =
>> =
>> =
>> =
>> =
>> =
>> =
>> =====================================================================
>> Package                 Arch       Version           
>> Repository        Size
>> = 
>> = 
>> = 
>> = 
>> = 
>> = 
>> = 
>> = 
>> =====================================================================
>> Updating:
>> bind                    x86_64     20:9.2.4-28.0.1.el4  sl- 
>> errata         596 k
>> bind-chroot             x86_64     20:9.2.4-28.0.1.el4  sl- 
>> errata          35 k
>> bind-devel              x86_64     20:9.2.4-28.0.1.el4  sl- 
>> errata         2.3 M
>> bind-libs               i386       20:9.2.4-28.0.1.el4  sl- 
>> errata         567 k
>> bind-libs               x86_64     20:9.2.4-28.0.1.el4  sl- 
>> errata         643 k
>> bind-utils              x86_64     20:9.2.4-28.0.1.el4  sl- 
>> errata         150 k
>> caching-nameserver      noarch     7.3-3.0.1.el4_6  sl- 
>> errata          22 k

This is not a problem with BIND. This is actually the behavior you  
requested when caching-nameserver was installed initially. I imagine  
the named.conf file was then changed extensively for an authoritative  
configuration and the existence of this package was forgotten.

The purpose of this package is solely to reconfigure BIND as caching  
only, dropping any authority it holds for a particular zone -- it will  
happily do so when updated. This package should never be installed on  
a machine acting as an authoritative DNS server.

Cheers,
Sam
--
Samuel Halicke		[log in to unmask]
FNAL/CD/SF/FEF		FCC/252/U
(T): 630.840.4308	(P): 630.266.0042

ATOM RSS1 RSS2