On 26/07/12 15:32, Steve Thompson wrote:
Samba 4.0.0beta4, CentOS 6.3.
It seems to me that when samba updates its DNS entries by processing a
dns_update_list entry such as:
A ${DNSDOMAIN} $IP
then:
(1) it is using the Kerberos realm name for DNSDOMAIN rather than the
DNS domain name. Indeed, it seems to me that there is quite a bit of
confusion between the two throughout Samba4.
(2) when a second or third DC is added, the value for $IP inserted in
the second or third DNS is the IP address of the first DC, not that of
the second or third. Huh?
I would _like_ the realm name and the DNS domain name to be the same,
but it appears that one cannot do that: bind9 will no longer start, as
I observed and reported previously.
Steve
Bind9 will not start if you set it up before provisioning Samba4, you
will end up with two zones, one will be the flat file you created and
the other will be the dlz file created by Samba4 and they will clash.
Provision Samba4 then add any servers, workstations etc to the dns
domain (and yes, the realm can be the same as the dns domain, i.e. they
both can be example.com). To add to the bind9 dlz file, use samba-tool
dns add <server> <zone> <name> <A|AAAA|PTR|CNAME|NS|MX|SRV|TXT> <data>
Try samba-tool dns add --help
Rowland
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
