Ryzen 7 2700x server build - DHCP and DNS on Windows Server 2016 or PFSense?

[Kalm_Traveler]

I finally decided what to use (sold a bunch of old parts) and have:

Ryzen 7 2700x

32gb of 3200mhz DDR4

Asus x470 Pro motherboard

1tb Samsung 960 Pro nVME ssd boot drive

reusing my old pair of 4tb Seagate desktop HDDs for now

2 port gigabit Intel NIC

EVGA Geforce GT 710 2gb graphics card

Corsair HX750 PSU

EVGA 280mm AIO

Cooler Master HAF XB Evo case

 

Anywho, off the bat I'll be putting VMWare ESXi on it, then setting up at least PFSense and Windows Server 2016 Datacenter in their own VMs.

 

Since I know PFSense can do DHCP and DNS, I'm just wondering if it would make any difference to have Windows Server do those instead?

[Falconevo]

8 hours ago, Kalm_Traveler1 said:

I finally decided what to use (sold a bunch of old parts) and have:

Ryzen 7 2700x

32gb of 3200mhz DDR4

Asus x470 Pro motherboard

1tb Samsung 960 Pro nVME ssd boot drive

reusing my old pair of 4tb Seagate desktop HDDs for now

2 port gigabit Intel NIC

EVGA Geforce GT 710 2gb graphics card

Corsair HX750 PSU

EVGA 280mm AIO

Cooler Master HAF XB Evo case

 

Anywho, off the bat I'll be putting VMWare ESXi on it, then setting up at least PFSense and Windows Server 2016 Datacenter in their own VMs.

 

Since I know PFSense can do DHCP and DNS, I'm just wondering if it would make any difference to have Windows Server do those instead?

pfSense has a far better DHCP interface than pfSense does so I would recommend using pfSense for DHCP.

Are you planning on creating a Windows Domain, if so you will need to set the DNS in the DHCP pool to be the domain controller(s).

[Kalm_Traveler]

39 minutes ago, Falconevo said:

pfSense has a far better DHCP interface than pfSense does so I would recommend using pfSense for DHCP.

Are you planning on creating a Windows Domain, if so you will need to set the DNS in the DHCP pool to be the domain controller(s).

I'm a little bit confused - assuming you meant one of those 3 pfSense's to be Windows? I'm familiar with Windows Server's DHCP interface from work, but I have never used pfSense yet if that makes any difference.

 

Haven't thought about creating my own domain yet (actually now that you mention it I'm not sure if 10 Pro clients can even join a domain?) but that is good to know.

[Falconevo]

 

33 minutes ago, Kalm_Traveler1 said:

I'm a little bit confused - assuming you meant one of those 3 pfSense's to be Windows? I'm familiar with Windows Server's DHCP interface from work, but I have never used pfSense yet if that makes any difference.

 

Haven't thought about creating my own domain yet (actually now that you mention it I'm not sure if 10 Pro clients can even join a domain?) but that is good to know.

lol sorry, that was me being retarded

 

pfSense has a better DHCP interface than windows.  Use pfSense for DHCP and Windows for DNS (if you are using a domain)

10 Pro clients can join a domain

[Blake]

20 hours ago, Kalm_Traveler1 said:

-snip-

Since I know PFSense can do DHCP and DNS, I'm just wondering if it would make any difference to have Windows Server do those instead?

10 hours ago, Falconevo said:

 

pfSense has a better DHCP interface than windows.  Use pfSense for DHCP and Windows for DNS (if you are using a domain)

10 Pro clients can join a domain

Why not both?

What sort of use case is this going to be for? Education? Dev Boxes? Prod?

Did you want a flat network toplology? or a little 'sub-domain' inside your home network?

 

Setup windows box/network (on there own vlan if you wish), have the DHCP/DNS on the windows server box forward DNS requests via the pfsense box.

DHCP isn't a requirement for AD, but makes it easier, Same with DNS.

 

[Kalm_Traveler]

3 hours ago, Blake said:

Why not both?

What sort of use case is this going to be for? Education? Dev Boxes? Prod?

Did you want a flat network toplology? or a little 'sub-domain' inside your home network?

 

Setup windows box/network (on there own vlan if you wish), have the DHCP/DNS on the windows server box forward DNS requests via the pfsense box.

DHCP isn't a requirement for AD, but makes it easier, Same with DNS.

 

use case is half for my learning, half because I want an always-on file share that isn't anywhere near my room, and network-wise I want to build out a 3 AP Ubiquity dual band setup around the house for better coverage with lower broadcast strength, and QoS to throttle my renters without hamstringing me. 

Up until now, I've been using a consumer wifi/router and had an i5 7600 desktop running Windows 10 Pro just idling along in the basement for file storage.