Op 03-12-2024 om 20:44 schreef Anders ?stling:>
>> On 3 Dec 2024, at 20:00, Kees van Vloten via samba <samba at
lists.samba.org> wrote:
>>
>>
>> Op 03-12-2024 om 19:46 schreef Anders ?stling via samba:
>>> Good evening folks
>>>
>>> I read this statement in the wiki regarding Bind9
>>>
>>> "You must not add the AD domain forward or reverse zone
records to the
>>> named.conf files, these zones are stored dynamically in Ad"
>>>
>>> This means that administration software like Webmin can't be
used with the
>>> samba/bind combo, and zones must be managed exclusively with
"samba-tool
>>> dns" .
>> This is true for the Active Directory dns-domains and the reverse zones
that go with it.
>>
>> Any other thing can safely managed with bind directly. I am thinking of
forwarding for specific domains to specific dnsservers, dns-views and so on (as
long as it does not work on the AD-dns-domain(s)).
>>
>> Do note that the AD domains are replicated though LDAP to all DCs, and
for everything in bind you have arrange synchronization over all binds on a DC
yourself.
>>
> Manage several zones with different tools sounds like a bad idea (for my
use case). So I think I will stick to a single domain/zone and use the internal
DNS.
>
> Also, I choose to look at the glass as half full since I managed to learn a
bit about bind when I configured it in a working master/slave setup with
automatic zone transfers :)
If?Samba's builtin DNS covers your requirements, then that is indeed the
best way to go.
- Kees.
>
>>> So what is the upside/benefit with using Bind9 compared with using
Sambas
>>> internal dns?
>> The above: with bind you have more functionality than with Samba's
internal DNS.
>>
> Thanks Kees
>
>> - Kees.
>>
>>
>> --
>> To unsubscribe from this list go to the following URL and read the
>> instructions: https://lists.samba.org/mailman/options/samba