[Samba] Some questions about Samba as a DC.

[Jason Long]

Thank you.
Consider an internal network that uses Windows server for Active Directory, DHCP and DNS services. Clients use a domain name to join to the internal network and Windows server gives clients a username and password for logging to the system, an IP and a DNS address.
Could Samba provide all of these features?
I think Samba couldn't provide DHCP service!






On Monday, April 26, 2021, 11:18:10 PM GMT+4:30, Rowland penny via samba <samba at lists.samba.org> wrote: 





On 26/04/2021 19:30, Jason Long via samba wrote:
> Hello,
> I want to use Samba as a DC on the Fedora Server and I have some questions:
>
> 1- Could Samba act like a DNS Server?


It already does.

>  If yes, then could it provide all features of the Windows DNS service?


As far as I am aware, it does provide the same features as a Win DC and 
can be managed from Windows.

>
> 2- For an internal network, is Samba DNS enough to provide DNS service or BIND is better?


AD dns is designed to provide dns to the AD domain, anything outside the 
AD domain should be forwarded to an external dns server. If you already 
have an existing dns server, then your clients can still use this dns 
server, provided it forwards all dns searches for the AD domain to a dns 
server on a DC. Best practice, if you have an existing registered dns 
domain, for instance: example.com , is to use a subdomain of that e.g. 
ad.example.com

There are pro's and con's of using either dns server, the internal 
server is easier to set up, but Bind9 is more robust and seems to be 
better for multiple DC's

Rowland


Rowland




-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba