DNS name does not exist

[Guest]

Hello, can anyone help me with the following problem:

I have installed Windows 2000 server with Active directory but without DNS.
After this, I would like to make a windows 2003 server an additional domain
controller. When I want to configure and installing this, I get a message
"DNS name does not exist". So, I thought, I'll have to install DNS on the w2k
server and the problem is solved. Not...
This is the message I'll get from the w2k3:

-----------------------
The following error occurred when DNS was queried for the service location
(SRV) resource record used to locate a domain controller for domain
care4go.nl:

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.care4go.nl

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:

192.168.40.18

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

care4go.nl
nl
.. (the root zone)

For information about correcting this problem, click Help.
-----------------

What can I do, to solve this problem.
When I give via system properties, network identification, properties,
domain; the domain name, I type the right domain name; and this works. How is
this possible?

Thanks in advance..

 

[Kevin D. Goodknecht Sr. [MVP]]

In

Hello, can anyone help me with the following problem:

I have installed Windows 2000 server with Active
directory but without DNS.

This was you big mistake Active Directory requires DNS, and all machines
must use the AD DNS server only in TCP/IP properties.

That being said, you said you installed DNS, did you point the DC to its own
private address for DNS only as it should?
If not, do so, restart the netlogon service and run ipconfig /registerdns
Install the server support tools from the CD and run netdiag /fix and run
netdiag /test:dns /v to verify DNS registrations.

You should be able to add the second DC then, if the second DC is using the
first for DNS. Please leave your ISP's DNS out of the picture, unless you
make them a Forwarder on the Forwarders tab in DNS.

300202 - HOW TO: Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/?id=300202&FR=1

825036 - Best practices for DNS client settings in Windows 2000 Server and
in Windows Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;825036

323380 - HOW TO: Configure DNS for Internet Access in Windows Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;323380

 

[Kevin D. Goodknecht Sr. [MVP]]

In

Thanks for your reply..

It looks like you may be using your local DNS server but apparently it does
not have a forward lookup zone named "care4go.nl"

See this:

DNS test . . . . . . . . . . . . . : Failed
Interface {0CA5583E-7160-4C2A-8EBD-1F121C83743A}
DNS Domain:
DNS Servers: 192.168.40.18
IP Address: 192.168.40.18
Expected registration with PDN (primary DNS
domain name): Hostname: ts2000.care4go.nl.
Authoritative zone: care4go.nl.
Primary DNS server: ns1.demon.nl 194.159.73.6<---this is the

public authoritative DNS server for care4go.nl.

Authoritative NS:194.159.73.6 194.159.176.4<----These are the public servers for this domain
Update is not allowed in zone care4go.nl..<--------

Open the DNS console open Forward lookup zones, start the new zone wizard
make it AD integrated or standard primary, name the zone care4go.nl. After
the zone is created on the zone properties, General Tab allow dynamic
updates "Yes" restart the netlogon service and run netdiag /fix
Then it should pass the DNS test and logon should be quicker.