AD + DNS + Exchange planning question...

[nrooke]

Hi, there is a missing "link" in my head when it comes to Exchange and DNS planning. We plan to eventually use an exchange server for mails. Our domain name(company.com) is hosted by an ISP.
I've setup AD to use "company.com" but when it comes to configurig the DNS, everything fails! Can't join the domain using another PC or server: reports a DNS error.
Anyone can point me on how should I configure my DC (incl. AD, DNS) in this scenario? Have to keep in mind the exchange server will come into place eventually.
I'm kind of "lost" here. I "feel" like to solution is really simple but can't see it!
Thx!

 

[unclerico]

the initial setup of DNS was successful correct? You can go into the DNS console and go into company.com forward lookup zone? First of all, what is set in the Primary DNS Server area in the NIC on the DNS server? Are you clients set to use DHCP or static? Either way, what are they using for the Primary DNS address? Also, what is the exact error message?

I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)

 

[nrooke]

You're right. DNS initial setup is fine. In the forward lookup zone I did put the name servers of my ISP. The primary DNS server area in the NIC points to my DNS server itself. Clients use DHCP and the primary DNS address is my DNS server.
The problem occurs when I try to setup a secondary DC for my domain or when I want to join the domain (I changed the original domain name to "domain.net":
======================================================
The following error occurred when DNS was queried for the service location (SRV)
resource record used to locate a domain controller for domain domain.net:

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.domain.net

Common causes of this error include the following:

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

10.1.101.3

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

domain.net
net
. (the root zone)

=======================================================

I've tried the following command: "netdiag /fix" but this returned this error: "DNS error code 0x00002339"

As if AD needs the DNS to be the SOA. Since the SOA is hosted my DC cannot write records to the ISP DNS servers... Is that right? or am I completely off track!?

Would the solution be to point the name servers at my ISP to my DNS server or is there another solution?

Thx!
Norm

 

[unclerico]

so what do you see when you expand to the following in your forward lookup zone:

_ldap._tcp.dc._msdcs.domain.net? do you see your _ldap SRV record pointing to your current DC?

Your ISP DNS addresses should be set as conditional forwarders.

Try to right click on the _msdcs.domain.net and choose reload

I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)

 

[nrooke]

Hi unclerico!
Ok... I did not have the _msdcs ; _sites ; _tcp ; _udp entries in my DNS! I guess something went wrong when I ran dcpromo. But, let's not blame everything on Microsoft!
Where I got confused is between my current ISP (the one that provides the internet connection) and where my domain is hosted! (two different things in my setup!) Why keep it simple when you can do complicated stuff!
I finally, ran dcpromo to demote the server, rebooted and then run dcpromo again (for the fifth time since yesterday!) And guess what? It now works! What changed for the last dcpromo are my "prefered DNS servers" in TCP/IP settings. I used the ones from my ISP not the ones from the Hosting company. Guess there was some kind of a fight between their DNS servers and mine.
Anyways, it's now fixed and I have two servers running. I've monitered the eventvwr and it'a ll smooth!
Thx for your time! It is very appreciated... it did spark something that put me on the right track!
Have a good day!
N. Rooke