Re: Pb with bind

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, 2005-09-04 at 16:07 +0200, François Patte wrote:

> Bonjour,
> 
> I tried to have named working for a private network but failed and the
> message in the log file is quite cryptic for me:
> 
> 
> Sep  4 18:45:58 localhost named[4098]: starting BIND 9.2.4 -u named
> Sep  4 18:45:58 localhost named[4098]: using 1 CPU
> Sep  4 18:45:58 localhost named: Démarrage de named succeeded
> Sep  4 18:45:58 localhost named[4098]: loading configuration from
> '/etc/named.conf'
> Sep  4 18:45:58 localhost named[4098]: listening on IPv4 interface lo,
> 127.0.0.1#53
> Sep  4 18:45:58 localhost named[4098]: listening on IPv4 interface
> eth1, 192.168.2.1#53
> Sep  4 18:45:58 localhost named[4098]: listening on IPv4 interface
> eth0, 192.168.1.5#53
> Sep  4 18:45:58 localhost kernel: audit(1125839758.430:0): avc:
> denied  { read } for  pid=4099 exe=/usr/sbin/named name=root dev=hda10
> ino=137955 scontext=root:system_r:named_t tcontext=root:object_r:var_t
> tclass=file
> Sep  4 18:45:58 localhost named[4098]: could not configure root hints
> from 'root': permission denied
> Sep  4 18:45:58 localhost named[4098]: loading configuration:
> permission denied
> Sep  4 18:45:58 localhost named[4098]: exiting (due to fatal error)
> 
> 
> 
> What's the meaning? and how to solve this problem.

Try:
# restorecon -R /var/named

> I have configurated named with FC1 without any problem and tried to do
> the same with FC3, but it doesn't work!

I think you may have edited a configuration file and then moved it into
place under /var/named; that will result in a file with the wrong
security context, which is the problem you have here.

Paul.
-- 
Paul Howarth <paul@xxxxxxxxxxxx>


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux