Question

Locked

Unable to join domain, receive domain controller not found error

By ahourigan ·
I recently had some problems with my internet upgrade and had to change the DNS entries on my DNS servers ( which are 2 seperate machines running win server 2003).
since then, i have not been able to add any xp pro machine to the domain, i receive an error. I have one server as the domain controller and 2 other machines serving as DNS servers. Is there something that i need to update on my domain controller when i changed the DNS entries on the DNS servers? Anyone else experience something similiar?

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

What exactly did you change on your DNS servers? -nt

by cypher.msix In reply to Unable to join domain, re ...
Collapse -

DNS ENTRIES

by ahourigan In reply to What exactly did you chan ...

I changed the DNS IP entries, AT&T made an upgrade and i was having internet issues, as a result i had to change the DNS IP's. Since i made that change on the DNS servers, i have not been able to add a machine to the domain. I am able to ping everything on the network prior to the change.

Collapse -

Questions

by cypher.msix In reply to DNS ENTRIES

The DNS IPs that you changed, I'm assuming were the forwarding IPs to AT&T's DNS IPs? Have your internal IPs and FQDNs of your DNSs changed at all?

What is the exact error message that you are getting from the client machines?

I would start by double-checking your DNS settings and making sure those IPs are accurate, and that there weren't any other changes that were made as a result.

Collapse -

error message verbatim...

by ahourigan In reply to Questions

Yes, they are fowarding to AT&T's IP's and no the IP's internally did not change. We are on Legacy Static, not PPoE. Im almost certain it has something to do with the DNS change that i made, but i cant pinpoint where the problem lies.
Here is the exact error...


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 DPERF 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 DPERF:

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.DPERF

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:

DPERF
. (the root zone)

For information about correcting this problem, click Help.

Back to Networks Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums