Quantcast
Channel: We Got Served Forums - New Posts
Viewing all articles
Browse latest Browse all 5022

Dns And Dhcp On A Home Lan With Ws2012 Essentials

$
0
0

Hi,

 

Like many pople here I've installed WSE2012 as a replacement for WSH2011 (and loving it :) ).

However, whilst WSH2011 could be viewed as a "stripped down" Server, WSE2012 is "full fat" and it has lots of stuff that whilst they may not be needed to replace WHS2011 are necessary for a happy WSE2012. 

 

Case in point - DNS and DHCP.

 

My setup for these is shown below - anybody care to comment and/or suggest changes...

 

DHCP - Handled by my Router. Switched off in WSE2012. I suspect that this is going to be fairly standard for most home installs. I use fixed address allocation based on MAC address, I have 40+ (at the last count) IP addressable devices and I find it very useful to be able to group the devices into known ranges- 192.168.1.nn: Routers & switches (01-09), Servers (10 -19), PCs (20 - 39), Smartphones (40-49), TV & streamers (50-59), Tablets (60-69), Others (70-79), VMs (80-89).

 

DNS - Primary DNS handled by the Router. DNS enabled on WSE2012 (secondary DNS).

 

The DNS spec handed out by the router just points at itself. Would it be sensible to add the WSE2012 DNS as a secondary DNS?

I'm thinking here that the WSE2012 is going to be using FQDNs like PC1.DOMAIN.local and currently any PC on the network that tries to ask the Router to resolve that name is going to get "not found" as a response.

 

Comments?


Viewing all articles
Browse latest Browse all 5022

Trending Articles