[CentOS] New CentOS DNS Server woes [SOLVED]
centos at swhi.net
centos at swhi.net
Mon Aug 6 02:11:20 UTC 2007
Les Mikesell wrote:
> centos at swhi.net wrote:
>> Les Mikesell wrote:
>>> Ray Leventhal wrote:
>>>>>>
>>>>>> Aug 5 14:10:08 sunspot named[5263]: dumping master file:
>>>>>> /var/named/chroot/var/named/slaves/tmp-sTsIWElBLR: open: file not
>>>>>> found
>>>>>>
>>>>>
>>>> Thanks, Craig. That sure made sense to do, but seemingly not the crux
>>>> of the issue.
>>>
>>> If named is running chroot, shouldn't the files be named from its
>>> perspective after the chroot - i.e. /var/named/slaves/* instead of
>>> /var/named/chroot/var/named/slaves/* like you see them? What does
>>> your "directory" entry say in named.conf?
>>>
>> [root at sunspot etc]# pwd
>> /var/named/chroot/etc
>> [root at sunspot etc]# more named.conf | grep swhi
>> zone "swhi.net" { type slave; file
>> "/var/named/chroot/var/named/slaves/db.swhi.net"; masters {
>> 64.135.16.10; };};
>> zone "swhi.us" { type slave; file
>> "/var/named/chroot/var/named/slaves/db.swhi.us"; masters {
>> 64.135.16.10; };};
>> zone "swhi.ws" { type slave; file
>> "/var/named/chroot/var/named/slaves/db.swhi.ws"; masters {
>> 64.135.16.10; };};
>> [root at sunspot etc]#
>>
>>
>> Am I understanding that the zone transfer requests should read
>> "/var/named/slaves/db.<domain>.net> {xxx.xxx.xxx.xxx;};};
>>
>> Thanks, Lee...I appreciate your help
>>
>
> Yes, the filename can be relative to the directory mentioned in the
> options section or absolute, but either way it has to take the chroot
> location into account, so omit the /var/named/chroot part.
>
That was absolutely the trick.
Thank you again, Lee
More information about the CentOS
mailing list