samba - Dec 2015 - After joining domain, Samba uses the workgroup name, not the FQDN when running the net ads command

On 03/12/15 20:45, Jonathan S. Fisher wrote:
> Ok, I really do think that line is significant, I checked in AD and my 
> sitename is "Default-First-Site-Name"
>
Words fail me, unless you explicitly set your site name when you 
provision, your site name will be "Default-First-Site-Name"

Rowland

>unless you explicitly set your site name when you provision
I guess we didn't. Is that an issue? I still wonder why that says
"null"
when, even if we used the default, our sitename is not null.
> well it obviously isn't working your way
To be sure, I took a packet capture. It shows the DNS is going straight to
the DCs, so in reality it is working the way you are describing: It is
ignoring the main DNS server. Here, check this out:

jonathan.fisher at freeradius:~$ nslookup whiskey.windows.corp.XXX.com
*Server: 192.168.127.131*
Address: 192.168.127.131#53

Name: whiskey.windows.corp.XXX.com
Address: 192.168.127.131


On Thu, Dec 3, 2015 at 2:49 PM, Rowland penny <rpenny at samba.org> wrote:
> On 03/12/15 20:45, Jonathan S. Fisher wrote:
>
>> Ok, I really do think that line is significant, I checked in AD and my
>> sitename is "Default-First-Site-Name"
>>
>>
> Words fail me, unless you explicitly set your site name when you
> provision, your site name will be "Default-First-Site-Name"
>
> Rowland
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>
-- 
Email Confidentiality Notice: The information contained in this 
transmission is confidential, proprietary or privileged and may be subject 
to protection under the law, including the Health Insurance Portability and 
Accountability Act (HIPAA). The message is intended for the sole use of the 
individual or entity to whom it is addressed. If you are not the intended 
recipient, you are notified that any use, distribution or copying of the 
message is strictly prohibited and may subject you to criminal or civil 
penalties. If you received this transmission in error, please contact the 
sender immediately by replying to this email and delete the material from 
any computer.

On 03/12/15 20:54, Jonathan S. Fisher wrote:
> >unless you explicitly set your site name when you provision
> I guess we didn't. Is that an issue? I still wonder why that says 
> "null" when, even if we used the default, our sitename is not
null.
>
No it isn't an issue, why are you now worrying about something that has 
nothing to do with your problem.
> > well it obviously isn't working your way
> To be sure, I took a packet capture. It shows the DNS is going 
> straight to the DCs, so in reality it is working the way you are 
> describing: It is ignoring the main DNS server. Here, check this out:
>
> jonathan.fisher at freeradius:~$ nslookup whiskey.windows.corp.XXX.com 
> <http://whiskey.windows.corp.XXX.com>
> *Server:192.168.127.131*
> Address:192.168.127.131#53
>
> Name:whiskey.windows.corp.XXX.com
<http://whiskey.windows.corp.XXX.com>
> Address: 192.168.127.131
>
>
>
Look, I will say it again, a bit more forcefully this time, *DO NOT USE 
ANYTHING BUT YOUR DCs AS NAMESERVERS ON YOUR AD CLIENTS*

Rowland