DNS Server

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Im about to set up my system with its domain, but was wondering if you can use the DC server as the DNS server too? if so, is it best to do this before or after the DC installation?

Currently i have a netgear router that performs my DNS and DHCP functions. I suppose i could just maintain this as the norm at present couldnt i?

Fergal

 

it does indeed look like it sets up the DNS on the system, so thats not too bad.

am i right in thinking that a DC can only be set for a single domain? so i couldnt have my root domain and the child domain on the same server???

 

sorry, what i meant what that if server1 is set as a DC for test.domain, then it couldnt also be the DC for int.test.domain (the child domain of test.domain).

 

Fergal, it's not so much an *if* as a *must* you must install DNS on your DC and point your clients and the DC itself at it. DNS for an Active Directory domain is more complex than just pure name resolution, so your Netgear box will not support local DNS queries and Active Directory needs local DNS support.

You can set up your new local DNS server to forward queries that it is not authoritative for (jargon for external queries to the Internet) by putting your ISPs (or other Internet DNS servers) IP addresses into the forwarders tab in the properties of your shiny new DNS server. This will make more sense once you have got it running locally.

 

I think that is not difference between you make DNS before making AD and you make DNS immediately after you make AD'.

But better you make it before making DC