DNS across two separate forests...?

[ben604]

Hello,

 

We're in the middle of building a new Domain on the same physical network as our existing Domain. We're using our active PDC as the DHCP and DNS server for the new Domain at the moment, to avoid any conflicts and it's working well, to a point. There is no trust setup between the two Domains, as far as their concerned, the other Domain doesn't exist.

 

When trying to connect a new client to the new domain, unless the new DC's IP address is manually entered into the DNS servers section in the NIC settings, it can't find the Domain.

 

Can I add an entry into either of the DC's so the clients will resolve the new Domain name without the fiddling?

[ben604]

Here's the error I'm getting:

 

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:\Windows\debug\dcdiag.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 "y.internal":

 

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.y.internal

 

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:

 

DC1 IP Address

DC2 IP Address

Domain 2 DC1 IP Address

 

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

 

y.internal

internal

. (the root zone)

 

 

We've got a forward lookup zone for the y.internal Domain on our x.local DNS server, but it's still not happy

[ben604]

worked this out...

 

I had added the new DC's IP address in the DHCP settings on the old DC, but it was 3rd in that list. Moving that up to the first in the list fixed the problem.