Description of problem:
In Fedora 10, /var/named/chroot/etc/named.conf is labeled with the name_conf_t type:
file_contexts:/var/named/chroot/etc(/.*)?       system_u:object_r:named_conf_t:s0

In rawhide, /var/named/chroot/etc/named.conf is labeled with the etc_t type:
file_contexts:/var/named/chroot/etc(/.*)?       system_u:object_r:etc_t:s0

In rawhide, /etc/named.conf is labeled with the named_conf_t type:
file_contexts:/etc/named\.conf  --      system_u:object_r:named_conf_t:s0

Should named.conf use the named_conf_t type regardless of where it is?

Version-Release number of selected component (if applicable):
selinux-policy-3.6.5-3.fc11.noarch
selinux-policy-targeted-3.6.5-3.fc11.noarch

How reproducible:
Always.

Steps to Reproduce:
1. yum install bind bind-chroot
2. cp /etc/named.conf /var/named/chroot/etc/
3. restorecon -R -v /var/named/chroot/etc/
  
Actual results:
/var/named/chroot/etc/named.conf labeled with etc_t type.

Expected results:
/var/named/chroot/etc/named.conf labeled with named_conf_t type?