Web lists-archives.com

Re: [Samba] Which DNS to use for DHCP hostname/IP updates from non-AD & AD nodes?

With Linux DHCP + Bind it was possible to have the DHCP server dynamically update Bind as new clients appeared. I don't need the clients themselves updating DNS records directly. For those few nodes using static IP addresses and not on the AD domain, I'm fine with having to manually enter their A/PTR records into the DNS database. IIRC normal MS Windows AD DC allows for nodes that are joined to the AD domain and have static IP addresses to register with DNS automagically because they are trusted.

Really I just need the DHCP to give out IP and some how have those nodes resolve by name through DNS. How that happens is totally flexible. I need to support nodes on the AD domain and those that are standalone.

On 02/13/2018 03:39 PM, lingpanda101 via samba wrote:
On 2/13/2018 3:07 PM, Ken McDonald via samba wrote:
I am considering which DNS implementation and cannot determine exactly when someone should use the Bind9 manner with BIND9_DLZ Module.

For my purposes, I will have AD and non-AD nodes on the network using either DHCP or static IP addresses. Some will be Windows & Linux clients joined on the Samba AD domain for logins. Some will be Windows & Linux clients that are standalone using either DHCP or static IP.

How should I best support this environment as a I move to a single AD domain setup with Samba4? I don't need to migrate anything.

In the past, I have supported this arrangement by using DHCP to update DNS (Bind9) which worked great for hostnames (reported from clients) and IP addresses (allocated from DHCP server).

I've read through these wiki's but cannot determine how to choose.




My questions are:

1) Which DNS implementation should I use?

2) Will I be able to have the non-AD devices register their hostnames and IP addresses in the same domain that Samba AD is using? (mine will be the recommended subdomain.domain.com and I'd like all DNS entries for AD and non-AD to be in the subdomain)


Will your DHCP server be the one to register the clients DNS names and IP's? If so I vote to go with Bind. It's not difficult to switch between the internal and Bind if you want to change in the future.

As far as clients not associated to the domain and registering their IP's and names. Not sure if the DHCP server can be authoritative for them. In the past I have used the internal and let the clients update their own IP's and names with nonsecure DNS updates. I would advise against it though.

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