Chris Arnold wrote:
> Sloan wrote:
>
>> OK a quick example, with an imaginary domain called "lexusespanol.com" -
>>
>> In named.conf add a stanza like this:
>>
>> zone "lexusespanol.com" {
>> type slave;
>> file "lexusespanol.com.db";
>> masters { 172.16.121.119; };
>> };
>>
>> So we've specified the zone name (lexusespanol.com), the type (slave),
>> the name of the file containing the dns data (lexusespanol.com.db) and
>> the IP address of the master server from which we get the zone data
>> (172.16.121.119).
>>
>> The server (172.16.121.119) must be configured to allow zone transfers
>> with our dns slave server.
>>
>> Once these files are in place, and /var/lib/named is writeable by the
>> user "named", restart named and the magic should happen. Look for the
>> file to appear in /var/lib/named, and test the dns server to make sure
>> it can answer requests for that domain.
>>
> Yea, thats the way i have it configured and it seems that named will not
> start. I get an error about ldap.xx.so shared libs. We have zimbra mail
> server installed on this same system and it appears, after a search
> through the zimbra forums, that it has something to do with zimbra.
> Zimbra appears to be a hog and not able to install anything after zimbra
> is installed....
>
Ah yes, we looked at zimbra too, and found that after installing it,
ldap would not start, due to zimbra modifying the system-wide ld.so
config to load the zimbra libs, which are apparently missing some symbols.
Joe
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]