host -t SRV _ldap._tcp.dc._msdcs.subdom gives nothing, thats correct.
host -t SRV _ldap._tcp.dc._msdcs.subdom.dom.com is also correct.
My question is:>Is this normal domain name behavior? How do I make it
>consistent use of just the subdom part? Keep in mind that
>only the subdom part was used when provisioning the domain.
in /etc/resolve.conf
add:
search subdom
nameserver IP_OF_AD_SERVER
but before you do that.
type : hostname -f returns ..
should be .. hostname.(subdom).dom.com
hostname -d returns (subdom).dom.com
hostname -s returns hostname
If this doesnt match, you can fix it.
change the hostname ( in fqdn ) in /etc/hostname
then type: hostname -f /etc/hostname
test again.
>If the server thinks the domain name is subdom.dom.com should
>that be the entry in smb.conf for member servers?
then yes it should ( same as the /etc/krb5.conf )
>When users map drives from non-member systems, I assume that
>they will need to use subdom.dom.com vs just subdom
if you dns is working correct you can always use the fqdn.
Greetz,
Louis
>-----Oorspronkelijk bericht-----
>Van: dwerthmu at ctg.albany.edu
>[mailto:samba-bounces at lists.samba.org] Namens Werthmuller, Derek
>Verzonden: woensdag 8 januari 2014 20:39
>Aan: samba at lists.samba.org
>Onderwerp: [Samba] Samba4 AD DC Domain name question
>
>I've been working on setting up the Sernet 4.1x series samba
>builds for Centos 6.
>Provisioned via sudo /usr/bin/samba-tool domain provision
>--use-rfc2307 -interactive
>
>With the goal of providing authentication, user and group
>management with file and print services to Widows 7/8 clients,
>& authentication user and group management for Linux system users.
>
>The question is around my confusion of the official domain name.
>
>The domain name used on the DC in smb.conf as subdom
>
>When doing a DNS search for the name of the DC.
># host -t SRV _ldap._tcp.dc._msdcs.subdom
>Returns no values.
>host -t SRV _ldap._tcp.dc._msdcs.subdom.dom.com
>returns the records for the DC.
>
>When trying to add a windows 7 client as a domain member,
>using subdom returns can't find DC. But the use of
>subdom.dom.com allows the windows 7 client to be successfully
>added to the domain.
>
>My question is:
>Is this normal domain name behavior? How do I make it
>consistent use of just the subdom part? Keep in mind that
>only the subdom part was used when provisioning the domain.
>
>If the server thinks the domain name is subdom.dom.com should
>that be the entry in smb.conf for member servers?
>
>When users map drives from non-member systems, I assume that
>they will need to use subdom.dom.com vs just subdom
>
>Thanks
> Derek
>
>--
>To unsubscribe from this list go to the following URL and read the
>instructions: https://lists.samba.org/mailman/options/samba
>
>