Am Dienstag, den 26.10.2004, 22:18 +0200 schrieb Florin: > Dieter Sch�tze <[EMAIL PROTECTED]> writes: > > > Hi Florin, > > > and BTW, on mnf it's not /etc/named.conf file because bind is chrooted to > > > something like /var/lib/chroot-named ... > > > > > the correct path is /var/lib/named-chroot if you edit > > the /var/lib/named-chroot/etc/named.conf you will see something like > > this: > > -------------------------------------------------------------- > > #------------------------------------------------------------------ > > # DO NOT MODIFY THIS FILE! It is updated automatically > > # by the naat/backend. Modify the templates/etc/named.conf instead > > #------------------------------------------------------------------ > > # You should generate again your key using dnskey_gen from the bind > > package > > > > ------------------------------------------------------------------- > > > > So i was right to modify the template /etc/named.conf ;-) > > > > Regards > > > > Dieter > > you don't understand, if you enable the dns caching-only server then the > templates will apply and create the /var/lib/named-chroot/etc/named.conf > file ... this is the file used by the chrooted bind in mnf. But I agree > that the above commented message may be confusing ... > > my 2cts, > Florin, i put these entries only in the /etc/named.conf after i have activated the dns caching, but i have these entries also in the /var/lib/named-chroot/etc/named.conf. Is there a restart of the dns after reconnect and can this overwrite the /var/lib/named-chroot/etc/named.conf with the template in /etc or why i have these entries there.
Regards Dieter
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
