I installed bind-chroot with yum, which also pulled in the "bind" package. (I
already had bind-libs installed, since I already had bind-utils installed.)
During the installation, it gave me a lot of warnings that the "named" user did
After the installation, I tried "id named" and got "id: named: No such user".
I looked at the files in /var/named, and they were owned by the "root" user and
the "named" group.
I did an "rpm -e bind bind-chroot". I also did an "rm -rf /var/named; rm -f
Then I did "yum install bind-chroot" again. This time it succeeded with no
errors, and the /var/named/* files are correctly owned by named:named.
I'm attaching the log of the first time I tried to install and got the warnings.
Created attachment 124729 [details]
Yum Log of first BIND installation
This problem could have potentially occurred if some other group had the gid 25
before bind was installed - then the named group would not have been created,
and the named user would not have been created.
This is now fixed with bind-9.3.2-6 in Rawhide / FC-5 .
Also fixed with bind-9.3.1-16.FC4, to be released to FC-4 updates/testing today.
From User-Agent: XML-RPC
bind-9.3.1-16_FC4 has been pushed for FC4, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report.
All attempts to fix this bug are dis-allowed by our packaging policy.
Apparently, if your system disallows named user or group creation by
the bind package, then your system is in an invalid and unsupported