Hello Mr555,
If the client will join to the domain it needs a DNS server of the 2003 domain.
AD relies on DNS and needs it's own domain DNS server. Even with forwarding
to another DNS server it is not the domain DNS.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
[Quoted Text] > Hello everyone
>
> We are doing AD prove of concept testing at present. Our environment
> consist
> of Bind DNS, Novell and Windows 2003 Domains.
> Current DNS and DHCP server are running on Linux there are DNS record
> already exist in the bind DNS servers. Workstations do not join to the
> Windows domain. All Workstation authenticate via Novell. What we
> trying to
> achieve here is to migrate it to Windows 2003 domain, have all
> workstations
> join to the domain. But we are keeping the existing bind server and
> DHCP
> server.
> We installed 3 domain controllers. DNS is enabled on each of them and
> we have setup forwarding to the Bind DNS. Zone transfer is specified
> to all the bind DNS Servers .
>
> we perform nslookup to the new domain is all working fine.
>
> All workstation obtain ip address via Linux DHCP server. the DNS entry
> for the workstation is pointing to the bind DNS we try to joining 1
> of the test workstation to the Domain testdomain.test.com , we
> received the following error
>
> But if we change the DNS server address on the workstation to the
> windows 2003 DNS it works.
>
> I know most of you will say get rid of the Linux DNS box. Unfortunate
> we can't so any suggestion or work around will be much appreciate it
>
> 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 domain name gtr might be a NetBIOS domain name. If this is the
> case, verify that the domain name is properly registered with WINS.
>
> If you are certain that the name is not a NetBIOS domain name, then
> the following information can help you troubleshoot your DNS
> configuration.
>
> The following error occurred when DNS was queried for the service
> location (SRV) resource record used to locate a domain controller for
> domain testdomain:
>
> 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.testdomain
>
> Common causes of this error include the following:
>
> - The DNS SRV record is not registered in DNS.
>
> - One or more of the following zones do not include delegation to its
> child zone:
>
> testdomain
> . (the root zone)
> For information about correcting this problem, click Help.
>
|