Why does bind named have a double chroot?

Solution Unverified - Updated -

Issue

  • When named is started, it appears to create 2 chroot environments:
    [root@localhost named]# pwd
/var/named/chroot/var/named/chroot/var/named
  • The chroot directories even have the same inode number:
    [root@localhost named]# ls -1id /var/named/chroot /var/named/chroot/var/named/chroot 
403251 /var/named/chroot
403251 /var/named/chroot/var/named/chroot

Environment

  • Red Hat Enterprise Linux 6
  • bind-chroot-9.7.3-2.el6_1.P1.1.i686
  • bind-9.7.3-2.el6_1.P1.1.i686

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content