Best Practice for Setting up Domain Controller + DNS Server with FQDN
HI there,
I'm setting up a new Domain Controller, DNS, DHCP server from scratch. I'm wanting to do it in the best manner possible. I've been told that using proper FQDN is the best practice for several reasons. I attempted to use our FQDN 'mrdomain.co.nz' as the Domain Controller name, this also happens to be domain of our website (and company). This went through fine. However, i'm concerned this may not be the best practice as i've had a few wee issues with DNS & DHCP.
I'm interesting in hearing the pro's and con's of this method also.
I'm looking for some advice in this manner, and I'm sure more info will need to be provided.
Many thanks
I'm setting up a new Domain Controller, DNS, DHCP server from scratch. I'm wanting to do it in the best manner possible. I've been told that using proper FQDN is the best practice for several reasons. I attempted to use our FQDN 'mrdomain.co.nz' as the Domain Controller name, this also happens to be domain of our website (and company). This went through fine. However, i'm concerned this may not be the best practice as i've had a few wee issues with DNS & DHCP.
I'm interesting in hearing the pro's and con's of this method also.
I'm looking for some advice in this manner, and I'm sure more info will need to be provided.
Many thanks
ASKER
Thanks for that.
Regarding your statement on not using a public domain name. Is there any reason for this in particular? Do some people use it?
The other items we are all sorted on.
Regarding your statement on not using a public domain name. Is there any reason for this in particular? Do some people use it?
The other items we are all sorted on.
Basically, you do not want your Private Infrastructure directly accessible from the internet.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Guy asked for best practices, not security. Best practice is to not use your External Domain Name. You now have an environment you need to patch and hack to get to your website. Very messy. I think you heard what you wanted to hear.
Search for technet Domain Controller best practices. Plenty of info around.
With 2008, if you are using a single disk system, I am finding using one big C drive is the best option.
Also use something like mrdomain.local or mrdomain.priv . Not best practice to use your public domain name.
Think about your backup Domain Contoller.
Make sure your structure is adequate and think about your naming conventions.
Finally, don't be afraid to wipe your DC if you are not comfortable. It's good practice and cleaner.
Good Luck!!