BIND 9.1.0 on RHL 7.1- Interoperability with Windows DNS

Kevin Darcy kcd at daimlerchrysler.com
Wed Jul 25 01:20:30 UTC 2001


You're getting "permission denied" when named tries to write anything
into its working directory. Doesn't that give you any idea what the
problem may be? Hint: it has nothing to do with the OS running on the
other server.

By the way, 9.1.3 is the latest production release of BIND.


- Kevin

raza.siddiqui at uplister.com wrote:

> Hi: I recently installed Red Hat Linux 7.1. Now I'm trying to set up a
> slave server. There's something with BIND 9.1.0 in RHL 7.1. With the
> default named.conf, the named process doesn't start. /var/log/messages
> shows this :
>
> Jul 24 12:58:08 penguin named[21768]: starting BIND 9.1.0
> Jul 24 12:58:08 penguin named[21768]: using 1 CPU
> Jul 24 12:58:09 penguin named[21770]: loading configuration from
> '/etc/named.conf'
> Jul 24 12:58:09 penguin named[21770]: the default for the
> 'auth-nxdomain' option is now 'no'
> Jul 24 12:58:09 penguin named[21770]: no IPv6 interfaces found
> Jul 24 12:58:09 penguin named[21770]: listening on IPv4 interface lo,
> 127.0.0.1#53
> Jul 24 12:58:09 penguin named[21770]: listening on IPv4 interface
> eth0, 192.168.1.25#53
> Jul 24 12:58:09 penguin named[21770]: couldn't open pid file
> '/var/run/named/named.pid': Permission denied
> Jul 24 12:58:09 penguin named[21770]: exiting (due to early fatal
> error)
>
> Then, I added the pid-file entry to the named.conf file.
> pid-file "/var/run/named.pid";
>
> After that, the named process starts successfully (from
> /usr/sbin/named; /etc/rc.d/init.d/named still has a problem).
>
> Jul 24 13:49:57 penguin /usr/sbin/named[22060]: starting BIND 9.1.0
> Jul 24 13:49:57 penguin /usr/sbin/named[22060]: using 1 CPU
> Jul 24 13:49:57 penguin /usr/sbin/named[22062]: loading configuration
> from '/etc/named.conf'
> Jul 24 13:49:57 penguin /usr/sbin/named[22062]: the default for the
> 'auth-nxdomain' option is now 'no'
> Jul 24 13:49:57 penguin /usr/sbin/named[22062]: no IPv6 interfaces
> found
> Jul 24 13:49:57 penguin /usr/sbin/named[22062]: listening on IPv4
> interface lo, 127.0.0.1#53
> Jul 24 13:49:57 penguin /usr/sbin/named[22062]: listening on IPv4
> interface eth0, 192.168.1.25#53
> Jul 24 13:49:57 penguin /usr/sbin/named[22062]: running
> Jul 24 13:49:57 penguin /usr/sbin/named[22062]: dumping master file:
> tmp-XXXXMHODc4: open: permission denied
> Jul 24 13:49:57 penguin /usr/sbin/named[22062]: transfer of dummy.com'
> from 192.168.1.10#53: receiving responses: permission denied
> Jul 24 13:49:57 penguin /usr/sbin/named[22062]: transfer of dummy.com'
> from 192.168.1.10#53: end of transfer
> Jul 24 13:49:58 penguin /usr/sbin/named[22062]: dumping master file:
> tmp-XXXXIt55nF: open: permission denied
> Jul 24 13:49:58 penguin /usr/sbin/named[22062]: transfer of
> '1.168.192.in-addr.arpa' from 192.168.1.10#53: receiving responses:
> permission denied
> Jul 24 13:49:58 penguin /usr/sbin/named[22062]: transfer of
> '1.168.192.in-addr.arpa' from 192.168.1.10#53: end of transfer
> Jul 24 13:50:45 penguin /usr/sbin/named[22062]: dumping master file:
> tmp-XXXXejyStQ: open: permission denied
>
> Now the master server in this case is a Windows 2000 server. The zone
> is not Active-directory integrated. Its a standard zone. And the
> Windows DNS Server log shows a successfull zone transfer. But on the
> linux side, nslookup fails and the zone files are not created anyway.
>
> Any help would be highly appreciated. Its driving me nuts.
>
> Regards
> Raza Siddiqui





More information about the bind-users mailing list