Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have uninstalled, rebooted, reinstalled, added, removed, changed, reconfigured everything imaginable related to AD: DS and it refuses to configure via dcpromo.exe.

It sits at "Examining DNS configuration" for over an hour. It adds things to the dcpromoui.log such as:

dcpromoui F04.CB4 0245 19:10:32.078 Dns_CountParentNsRecordsForDomain NS Enumeration for mysite.comon parent . failed, returned 1722

dcpromoui F04.CB4 0246 19:10:32.078 Dns_CountParentNsRecordsForDomain performing NS Enumeration for mysite.comon parent .

I'm adding the role for AD: DS with the integrated DNS; I don't have a separate DNS role.

Any suggestions other than reconfiguration by hammer would be great.

share|improve this question
    
Is this the first DC you're trying to add to a new forest, or an additional DC that you're promoting? –  MDMarra Jul 12 '12 at 2:18
    
I'm playing with AD for the first time. So I guess I'm taking my domain and adding that to a new forest. Previously I configured it as corporate.mysite.com from a tutorial. I wanted to redo this as mysite.com instead this time, so I could have myserver.mysite.com instead of myserver.corporate.mysite.com or something crazy as the default. I could also quite possibly have no clue how to set this up correctly. –  Michael J. Gray Jul 12 '12 at 2:27
    
It seems to work just fine when I do "corporate.mysite.com". This is apparently the normal practice though. No clue as to why. –  Michael J. Gray Jul 12 '12 at 2:43
1  
Don't use ever a top-level domain name for your AD name unless you will never ever use that same name for an external website. –  MDMarra Jul 12 '12 at 2:46

1 Answer 1

up vote 0 down vote accepted

To resolve this I made AD responsible for corporate.mysite.com. I delegated authority for corporate.mysite.com from mysite.com's DNS to the corporate.mysite.com DNS.

When using mysite.com as the domain for AD, it simply hung indefinitely. Why? I don't really know. But I just know that any subdomain for mysite.com worked fine.

If someone has a deep explanation of why this is the case, I'll mark it as the answer.

share|improve this answer
    
We're you literally using mysite.com? –  MDMarra Jul 12 '12 at 11:03
    
I am confused. Are you asking a question or making a statement? It would be odd to ask "We are you literally using mysite.com?" Anyway, if you mean to ask if I'm actually using mysite.com, then no. –  Michael J. Gray Jul 12 '12 at 17:10
    
I did mean to say "were" instead of "we're". My iPad autocorrected it and I didn't catch the error. If that obvious typo confuses you, then I'd take a step back from Active Directory for a while :) –  MDMarra Jul 12 '12 at 17:11
    
I love auto correction. But anyway, AD seems like a great thing to step away from even when understanding your typo. I'm getting pretty deep into why people get mad at it, but also why others love it. Good times. :) –  Michael J. Gray Jul 14 '12 at 19:48

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.