Networking
--
Questions
--
Followers
Top Experts
Missing DNS entries in Active Directoy Domain Controller's DNS
I inherited a W2K AD Domain. The first additional XP workstation I tried to add to it I recieved this message.
The domain name domainname 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 domainname:
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.domai
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:
domainname
. (the root zone)
I then ran dcdiag and this is what I got.
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\se
Starting test: Connectivity
servername's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(klajlkajdf.lkjlkjdf.jlasd
be resolved, the server name (servername.domainname.net
to the IP address (x.x.x.x) and was pingable. Check that the IP
address is registered correctly with the DNS server.
......................... servername failed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\se
Skipping all tests, because server servername is
not responding to directory service requests
Running enterprise tests on : domainname.net
Starting test: Intersite
......................... domainname.net passed test Intersite
Starting test: FsmoCheck
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERV
5
A Good Time Server could not be located.
......................... domainname.net failed test FsmoCheck
I then logged onto the DC to check the DNS and all the _msdc,_sites,_tcp,_udp for the domain are not there.
My question is how do I create or recreate those records without manually entering each one?
The domain name domainname 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 domainname:
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.domai
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:
domainname
. (the root zone)
I then ran dcdiag and this is what I got.
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\se
Starting test: Connectivity
servername's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(klajlkajdf.lkjlkjdf.jlasd
be resolved, the server name (servername.domainname.net
to the IP address (x.x.x.x) and was pingable. Check that the IP
address is registered correctly with the DNS server.
......................... servername failed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\se
Skipping all tests, because server servername is
not responding to directory service requests
Running enterprise tests on : domainname.net
Starting test: Intersite
......................... domainname.net passed test Intersite
Starting test: FsmoCheck
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERV
5
A Good Time Server could not be located.
......................... domainname.net failed test FsmoCheck
I then logged onto the DC to check the DNS and all the _msdc,_sites,_tcp,_udp for the domain are not there.
My question is how do I create or recreate those records without manually entering each one?
Zero AI Policy
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
ASKER CERTIFIED SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
I could not agree more. Its not a test box. About 10 users right now access this DC for files and Exchange 2000 is running on it.
SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
I'd delete the DNS and start all over as well.....create an AD integrated zone...are there other Domain Controllers, b/c if replication is not working right, all hell breaks loose....especially when trying to introduce windows xp
Another thing is that you also need to create a reverse DNS zone for your IP range(s) in the server as well and then if your forward DNS zone is set up correctly and active directory integrated then a simple ipconfig /registerdns should do the trick provided that the dc (assuming the dns box is a dc) is pointed to itself as primary DNS server in it's network settings. the registerdns switch will work to add the entries dynamically. And since the server is a dc it will register all of the _ records that are required for AD operation...
Hope this helps!
D
Hope this helps!
D
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
I just had a similar problem to this. From the DNS server that is experiencing this issue:
Under the forward lookup zone -> _msdcs folder ensure you have an srv record for the server in question. In my case I was missing one of my DC. I got the guid from dcdiag and added the cname record manually. Replication kicked in right away.
Under the forward lookup zone -> _msdcs folder ensure you have an srv record for the server in question. In my case I was missing one of my DC. I got the guid from dcdiag and added the cname record manually. Replication kicked in right away.
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.
I will leave the following recommendation for this question in the Cleanup topic area:
Split: jayca {http:#10264442} & oBdA {http:#10265619}
Any objections should be posted here in the next 4 days. After that time, the question will be closed.
grblades
EE Cleanup Volunteer
I will leave the following recommendation for this question in the Cleanup topic area:
Split: jayca {http:#10264442} & oBdA {http:#10265619}
Any objections should be posted here in the next 4 days. After that time, the question will be closed.
grblades
EE Cleanup Volunteer
I had the same problem a few times, delete the forward look up zone, recreate it anew, making sure the old zone was completely purged from the active directory, after you recreate the zone, check the _MSDCS root, if there isnt an alias entry for each DC, open a DOS box anf type "net stop netlogon" after it has stopped, type "net start netlogon", this usually creates the alias entries in the MSDCS you need for the replication and DC name resolution.
On the DHCP, make sure you define entries for the DNS server, so that clients will register into your Active Directory DNS server, be sure you defined the zone as Dynamically updated, this way you can omit having to use WINS, unless you have hosts that do not support TCP/IP, you will have to keep the WINS, and an entry for it will have to be defined in the DHCP for hosts to register.
On the DHCP, make sure you define entries for the DNS server, so that clients will register into your Active Directory DNS server, be sure you defined the zone as Dynamically updated, this way you can omit having to use WINS, unless you have hosts that do not support TCP/IP, you will have to keep the WINS, and an entry for it will have to be defined in the DHCP for hosts to register.
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
the accepted answers are more than great. they are correct. but you could add the entries as well. deleting the "." would more help with security though, but it will get the job done.
If SRV records are missing from a zone, use the netdiag utility with the /fix switch. This will automatically create all the records you need for your zone.
You can download the netdiag utility from here:
http://www.microsoft.com/windows2000/techinfo/reskit/tools/existing/netdiag-o.asp
You can download the netdiag utility from here:
http://www.microsoft.com/windows2000/techinfo/reskit/tools/existing/netdiag-o.asp
I ran dcdiag /test:connectivy and got this
DC Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial non skippeable tests
Testing server: Default-First-Site-Name\MO
Starting test: Connectivity
MOE's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(fa32e0f0-0909-45be-a2ea-b
be resolved, the server name (Moe.montville.local) resolved to the IP
address (192.168.1.4) and was pingable. Check that the IP address is
registered correctly with the DNS server.
......................... MOE failed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\MO
Running enterprise tests on : montville.local
I inherited a nasty environment 50 + workstations in a mixed workgroup and domain(s) environment, trying to consolidate into one domain. Have one 2003 DC and one 2000 DC. When I first joined the 2000 machine to the domain and promoted it the pair hated each other (no replication). I did what squeekie suggested and wallah! replication. Thankyou!
willone
DC Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial non skippeable tests
Testing server: Default-First-Site-Name\MO
Starting test: Connectivity
MOE's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(fa32e0f0-0909-45be-a2ea-b
be resolved, the server name (Moe.montville.local) resolved to the IP
address (192.168.1.4) and was pingable. Check that the IP address is
registered correctly with the DNS server.
......................... MOE failed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\MO
Running enterprise tests on : montville.local
I inherited a nasty environment 50 + workstations in a mixed workgroup and domain(s) environment, trying to consolidate into one domain. Have one 2003 DC and one 2000 DC. When I first joined the 2000 machine to the domain and promoted it the pair hated each other (no replication). I did what squeekie suggested and wallah! replication. Thankyou!
willone
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
Networking
--
Questions
--
Followers
Top Experts
Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.