Description of problem:
bind-9.9.4-29.el7_2.1.x86_64 has a change that removed the -t option from named-chroot.service. As such, named-checkconf fails, and bind fails to start.

Version-Release number of selected component (if applicable):
bind-9.9.4-29.el7_2.1.x86_64

The faulty systemd unit seems to be: /usr/lib/systemd/system/named-chroot.service

It does a sanity check - but doesn't make it relative to the chroot:
ExecStartPre=/bin/bash -c 'if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/sbin/named-checkconf -z /etc/named.conf; else echo "Checking of zone files is disabled"; fi'

If you add the chroot directive in there (which it probably should have anyway), then all works:
ExecStartPre=/bin/bash -c 'if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/sbin/named-checkconf -z -t /var/named/chroot /etc/named.conf; else echo "Checking of zone files is disabled"; fi' 

While I don't have an RHEL reference, this is the change on the CentOS git import:
https://git.centos.org/blobdiff/!rpms!bind.git/d56ed2d3a2736a07a09c268f3b2607cca8f1b6ca/SOURCES!named-chroot.service