Соедините Клиент с доменом, не устанавливая DNS

If you have DHCP enabled on the network, you can have the DHCP server hand out the DNS Server address via DHCP options.

From Technet (assuming a Windows Server DHCP server):

Table 4.5 Default DHCP Options

Code

Option name

Meaning

6 DNS servers Specifies a list of IP addresses for DNS name servers available to the client

http://technet.microsoft.com/en-us/library/cc958929.aspx

If you are trying to support a BYOD scenario where clients come to you with a preconfigured network profile with access to public DNS, and you don't mind a bit of information disclosure, you could simply create the DC Locator record in public DNS.

Let's say your AD Domain FQDN is local.contoso.com, go ahead and create the following records in public DNS:

dc01.local.contoso.com                  A             [Domain Controller IP] 
_ldap._tcp.dc._msdcs.local.contoso.com  SRV  0 0 389  dc01.local.contoso.com

Now clients will be able to locate your domain controller when you join them to the domain.

But even then, after joining, you still have to provide the clients with a preferred DNS server address that can resolve your AD zones.

Вы также можете изменить настройки реестра клиента, чтобы не требовать локальной настройки DNS. Запустите редактор реестра (regedit.exe), перейдите по адресу:

HKLM\System\CurrentControlSet\Services\LanManWorkstation\Parameters

• создайте DWORD с именем DNSNameResolutionRequired со значением 0
• создайте DWORD с именем DomainCompatibilityMode со значением ] 1