I have just deployed a Win 2012 Server Essentials in a small network of about 15 workstations.
Out of the box, it came pre-configured with some common roles and features.
This greatly helped in a quick and smooth deployment.
I work on the principal that if it is not broken, don't fix it.
However, I am bugged by 2 issues for which I would welcome some experts' comments and advice.
1. DHCP server
Default installation comes without DHCP enabled.
Microsoft probably thought that this is non-essential inspite of the server being a domain controller.
I have left it at that, with client computers getting the IPs from a router.
It's working. Should I leave this alone?
2. DNS server
Not surprisingly, it comes enabled.
Clients computers all point to the server for authoritative DNS names resolution.
The server to itself (127.0.0.1)
Again this seems to be working (although I suspect that computers take a little longer to resolve external host names when browsing on the internet).
Should I add the ISP DNS server IPs as forwarders?
Or should I just leave it to just use root hints?
Would users have a speedier browsing experience?
Or in time, would the server DNS cache build up to such an extent that it will not make any significant difference?
There seems to be a lot of questions. But essentially, it is whether I should let sleeping dogs lie?