DNS delegation for this server cannot be created?

[Gilly2003]

Hi guys,

 

Hoping someone can help, paint the picture first:

 

two sites, HQ and Coal. HQ houses our primary 2008R2 DC with its secondary DC. Coal which is connected by VPN houses another child DC (server 2003) which replicates off primary DC in HQ.

 

I am replacing the Coal DC with a new server running 2012.

 

Trying to set the DC for Coal up in HQ, added AD DS and launched the wizard to promote to a DC:

 

• select add a DC to an existing domain (enter domain admin credentials)
  
• next I specify DC capabilities which are DNS and global catalog, also select site info which is coal. IT asks for directory services restore mode password which I assume can be anything entered as it lets me click next?
  
• then on DNS options screen I get:
  

 

 

Anyone help with what this is?

 

Any info would be greatly appreciated

Edited June 4, 2015 by Gilly2003

[mikkydoos]

Could be a slow link to the other DC if its going over a VPN. Or the credentials are not enough.

[Gilly2003]

But I am setting the new DC up in HQ before moving it physically to coal?

 

Or does it have to establish a connection with the current coal DC to do this?

[mikkydoos]

But I am setting the new DC up in HQ before moving it physically to coal?

 

Or does it have to establish a connection with the current coal DC to do this?

 

 

Wheres the primary DNS server located ? Or is Coal a replica of the DC at HQ ?

[Gilly2003]

The primary DNS is located in HQ and the current coal server replicates from it.

 

this new server I am trying to set up in HQ will replace the one at coal once I get it fully deployed

[mikkydoos]

Did you type in the FQDN. It can't find the HQ DNS server. Try connecting the new coal servers DNS console to the HQ server and see if you can connect and modify.

[Gilly2003]

The FQDN name on the deployment configuration screen already has the domain filled in?

 

Unless I am confusing the FQDN as also being the domain name?

 

The coal server can see the primary DC and browse its files etc so I am not sure as to how to proceed.

[kevin_lane]

Is this all one domain because you mentioned child domain so to me your telling me your trying to upgrade or add a secondary domain controller to the child domain or have I got that wrong sorry if I have that wrong also how have you setup the DNS settings on the new server

[Gilly2003]

Sorry, we are all one domain.

 

the current server in coal replicates off the primary DC in HQ

 

however i will be replacing the current coal server with the new 2012 server and I am basically asking how to prepare it as much as I can in HQ so as to make it a straight swap when i decommission the current in coal

 

sorry, maybe i didnt explain it properly

 

I am an aspiring system admin so abit of a newbie...

 

In my head I was adding the AD DS role which prompts me to then add a Dc role and launches the wizard for me to do so, i then get the error about DNS and parent zone.

 

But I am beginning to think I need to delegate DNS privilege to this new server before promoting it to a DC?

Edited June 4, 2015 by Gilly2003

[kevin_lane]

Well it depends becuase does the server you are replacing contains the fmso roles if not don't worry too much also what server is running DNS you should still be able to delegate permission to the server afterwards I think it should still let you continue.

[kevin_lane]

In 2008r2 and 2012 you really have a pdc (primary domain controller) however if you have a server that contains all the fmso roles you could called that the "primary" as you can now seize roles and transfer roles when dcs fail over (never been in that situation don't want to either ) when you add the new dc you can just add the dc and not the DNS but as long as you point the server to the primary DNS which hosts your .local zone you should be ok and then add the DNS at a later date if you are going off site wouldn't a read only dc be better for you ?