URGENT: MSDCS records registering directly under FWD lookup zone, not under FQDN name space.
I am under the gun and don't have time to research this. You might know the answer off the top of your head!! Need Quick help. Can you help me put the SRV records in the right spot? All X-d out data is my fully qualified domain name.
SRV records are registering in the wrong spot. This is jacking up my active directory and DFS and all other domain services. A picture is worth a thousand words. So, see it for yourself.
on this site 2x 2003R2 dcs with
New-Bitmap-Image.JPG
SRV records are registering in the wrong spot. This is jacking up my active directory and DFS and all other domain services. A picture is worth a thousand words. So, see it for yourself.
on this site 2x 2003R2 dcs with
New-Bitmap-Image.JPG
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Excellent:
Good input> I will delete the folders.
There was only one single record on the delgation for _msdcs folder. That record was a same as parent NS record. Other than that, I don't see the other records. Then, under the forward lookup zone msdcs group of records, it appears I have a complete set of SRV records. Since the delegation is incomplete, I am running into errors 4004 and 4015 DNS, along with problems with network logons, DFSR, access to domain services, ect....
You know what might have caused this guys? I don't want it to happen in the future.
Good input> I will delete the folders.
There was only one single record on the delgation for _msdcs folder. That record was a same as parent NS record. Other than that, I don't see the other records. Then, under the forward lookup zone msdcs group of records, it appears I have a complete set of SRV records. Since the delegation is incomplete, I am running into errors 4004 and 4015 DNS, along with problems with network logons, DFSR, access to domain services, ect....
You know what might have caused this guys? I don't want it to happen in the future.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Exactly. There have been a bunch of posts that the Msdcs folder have been delegated which causes replication issues.
Not quite sure why MS made it install like that for some domains, seems like a complication most admins in small businesses won't know how to deal with.
Ho hum...
Chris
ASKER
They ought to offer the ability for an author to grant more points for a quick resolve.
SWEEEEET GUYS!!! This did exactly what you said it would do. I will check up on delegations and see what I can do to prevent this in the future.
DARIUSQ, congrats on your first million. Looking forward to seeing you at 10 mill.
Chris, what can I say about your DNS skills?
SWEEEEET GUYS!!! This did exactly what you said it would do. I will check up on delegations and see what I can do to prevent this in the future.
DARIUSQ, congrats on your first million. Looking forward to seeing you at 10 mill.
Chris, what can I say about your DNS skills?
ASKER
Let me post this for everyone to see:
They ought to offer the ability for an author to grant more points for a quick resolve.
SWEEEEET GUYS!!! This did exactly what you said it would do. I will check up on delegations and see what I can do to prevent this in the future.
DARIUSQ, congrats on your first million. Looking forward to seeing you at 10 mill.
Chris, what can I say about your DNS skills?
They ought to offer the ability for an author to grant more points for a quick resolve.
SWEEEEET GUYS!!! This did exactly what you said it would do. I will check up on delegations and see what I can do to prevent this in the future.
DARIUSQ, congrats on your first million. Looking forward to seeing you at 10 mill.
Chris, what can I say about your DNS skills?
Glad we could help you out Chief :)
Chris
Anything for you Chief! Thanks!
FYI, had same issue and ran netdiag command from the 2003 DC and it repaired the DNS issues
I just saw that is was you. Delete both zones make sure if they are AD-integrated make sure you do it on both servers.