Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Joining a Domain Issue.

Status
Not open for further replies.

coaxnps

Vendor
Sep 11, 2007
33
US
Recieving the following error after installing Server 2008:

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

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

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:

BFCPlan
. (the root zone)

For information about correcting this problem, click Help.


IP Address: 192.168.160.103
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.160.1
DHCP Server: 192.168.160.1
Lease Obtained: 2/4/2010 3:24:26 PM
Lease Expires: 2/5/2010 3:24:26 PM
DNS Server: 10.10.1.13
WINS Server: 10.10.1.13
 
BTW I'm able to ping the 10.10.1.13 address and RDP to it, however I'm not able to resolve the server's name via ping.
 
Why is your 2008 server on the 192.168.160.x subnet yet your DNS on 10.10.1.x? What is the relationship between the two subnets?

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.

There are no more PDC's! There are DC's with FSMO roles!
 
192.168.160.X is a remote location that use to be able to connect to the old 2003 domain that was on the 10.10.1.X subnet. The new DC is on the 10.10.1.X and is also the DNS server.
 
Can you do nslookup for your domain? What results do you get.
Try nslookup > set type=all and your domain. What do you get?

What is FQDN of your domain? Where are the zones stored?

What is the server's IP address where you're getting the error message?

It looks like a DNS issue, which is easy to resolve, provided we have more details.

Can you post IP config of the affected machine?

Regards,

Michael.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top