Trouble joining domain

bobby_inboerne said 1 year, 1 month ago:

I get an error when trying to join my Server2 to my Server1 domain. Can you help? Thank you.

JustinC said 1 year, 1 month ago:

@bobby_inboerne

Can you give us some additional info? For example, what process are you using and what is the error you’re receiving? This will help us hopefully guide you in the right direction.

Of course, you can always contact our Support Team so that we can access your account and see if there’s a reason within your account it’s not working.

Either way, including the information I’ve asked for will help us assist you much more effectively.

bobby_inboerne said 1 year, 1 month ago:

Note: This information is intended for a network administrator. If you are not your network’s administrator, notify the administrator that you received this information, which has been recorded in the file C:Windowsdebugdcdiag.txt.

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain “biztechtx.biz”:

The error was: “DNS name does not exist.”
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc._msdcs.biztechtx.biz

Common causes of this error include the following:

- The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses:

10.1.0.1

- One or more of the following zones do not include delegation to its child zone:

biztechtx.biz
biz
. (the root zone)

krisl said 1 year, 1 month ago:

@bobby_inboerne

This is beyond the scope of support for GDCS, however I ran into this personally and the fix should be simple. All you need to do is change the DNS on the machine you are trying to join to your windows domain to use the domain controller (technically you have to point it to the AD controlled DNS server) as the DNS server. I am assuming that when you added the AD roll to your domain controller that you also configured that machine as a DNS server.

So on any machine that you are trying to join to the domain you should go to that machines network adapter and statically set the primary DNS server to the internal IP of your domain controller. If you have a second domain controller, then set the secondary DNS server to that IP.

What is happening is that the machine that you want to join to the Domain is using the network instance for DNS. But the Windows domain itself creates SRV records and other windows domain specific DNS entries. The network instance (10.1.0.1) knows nothing of these Windows Domain specific DNS records.
Additionally, on the AD controlled DNS you should verify that it will do external domain look ups against the network instance or whatever DNS server you wish to you use to resolve say Godaddy.com.