Why am I not able to join a computer to the domain when looking at the new DNS server?
I'm in the process of installing a new Windows 2003 Standard Ed. DC, transferring all services over from the old one, and removing the old server from the network.
So far I have installed AD and DNS on the new server, promoted it to the Global Catalog, transferred FSMO roles, and demoted the old server from being a Global Catalog. I have not yet demoted the old server by running dcpromo and removing AD because I have been working on Certificate Services first. That is where I'm at with the two servers.
I just took a client computer, configured the IP address to point at the new DNS server and tried to join the computer to the domain (allianceacademy), but I received the following error:
The domain name "allianceacademy" 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 an Active Directory Domain Controller (AD DC) for domain "allianceacademy":
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.allia
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:
192.168.91.16
- One or more of the following zones do not include delegation to its child zone:
allianceacademy
. (the root zone)
When I tried to add the same client to the domain name alliance.k12.ec it seemed to worked.
I then took a second client with the IP settins configured to look at the oringinal DNS server and joined it to the domain with allianceacademy.
How do I fix this discrepancy in the name of the domain? All the other clients on the network are joined to the allianceacademy domain - not the alliance.k12.ec domain. Are the two the same domain just named differently? What exactly is going on here?
So far I have installed AD and DNS on the new server, promoted it to the Global Catalog, transferred FSMO roles, and demoted the old server from being a Global Catalog. I have not yet demoted the old server by running dcpromo and removing AD because I have been working on Certificate Services first. That is where I'm at with the two servers.
I just took a client computer, configured the IP address to point at the new DNS server and tried to join the computer to the domain (allianceacademy), but I received the following error:
The domain name "allianceacademy" 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 an Active Directory Domain Controller (AD DC) for domain "allianceacademy":
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.allia
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:
192.168.91.16
- One or more of the following zones do not include delegation to its child zone:
allianceacademy
. (the root zone)
When I tried to add the same client to the domain name alliance.k12.ec it seemed to worked.
I then took a second client with the IP settins configured to look at the oringinal DNS server and joined it to the domain with allianceacademy.
How do I fix this discrepancy in the name of the domain? All the other clients on the network are joined to the allianceacademy domain - not the alliance.k12.ec domain. Are the two the same domain just named differently? What exactly is going on here?
Are the SRV records in DNS on the new domain controller? If not you can first try to restart the netlogon service. If that doesn't work you can run dcdiag /fix. If that doesn't work try running netdiag /fix.
ASKER
I looked in the forward lookup zone for an SRV record on both the old and new dns servers and I didn't find one on either. Is this the right place to look?
So if I restart the netlogon service on the new DC then that will automatically fix the SRV record issue?
So if I restart the netlogon service on the new DC then that will automatically fix the SRV record issue?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The Primary DNS Suffix is returning alliance.k12.ec so it looks like we good in that area.
Then you should be able to join the domain using alliance.k12.ec, the other is reliant on NetBIOS naming which is harder to support unless you have all the infrastructure for that in place (such as WINS servers).
Chris
ASKER
okay, that is good to know. I guess it just struck me as strange that I'm able to join the "allianceacademy" domain when i'm pointed to the old DNS server, but when I point to the new DNS server I can't - I have to use the "alliance.k12.ec" domain? I thought maybe something got messed up during the DNS and/or AD part of the server migration.
It shouldn't really matter which you point at because DNS can't resolve that name, it's reliant on NetBIOS which is always a lot of fun.
Chris
Chris