named + chroot

David Kramer dkramer at
Thu May 6 23:53:30 UTC 2004

I guess Im confused as to why you would hardlink those files versus dropping
them directly into your chroot environment.  I was always told for a pure
chroot environment that you MUST place all dependent files within the
chroot.  I've been running a public DNS for quite some time like that
without issues(KNOCK ON WOOD...)  At one point I think I was missing my
rndc.key reference within my named.conf file, once I corrected the path and
had that file within my chroot/etc/dir I was good to go.  Let me know if you
need more help with this.


> -----Original Message-----
> From: fedora-test-list-bounces at
> [mailto:fedora-test-list-bounces at]On Behalf Of Vibol Hou
> Sent: Thursday, May 06, 2004 4:49 PM
> To: fedora-test-list at
> Subject: named + chroot
> I initially installed the bind package alone and then I installed
> bind-chroot and caching-nameserver.  This caused rndc to start giving
> errors which I traced back to bind-chroot not containing the appropriate
> named.conf and rndc.key files;  to resolve this, I hardlinked the
> /var/named/chroot/etc/named.conf file to /etc/named.conf and
> /var/named/chroot/etc/rndc.key to /etc/rndc.key.
> Has anyone else experienced this problem?
> -Vibol
> --
> fedora-test-list mailing list
> fedora-test-list at
> To unsubscribe:

More information about the test mailing list