Considerations for creating a domain controller with DNS in home lab?
-
I have pfSense running in a VM hosted in my home lab and I'm using it for DNS and DHCP services. I have created a Windows domain controller in the lab with the same DNS suffix as pfSense. So I have pfSense DNS configured like so:
Should I create my Windows domain as duck.loc too (netbios DUCK) or something else? Anything else I should consider?
-
you should let the windows DC handle DNS for the clients. Easiest way is to add a forwarder for the domain "duck.loc" on pfsense to point to the Windows DC ip.
-
Any member of domain should only use domain dns.. Ie your DC.. This should really be the dhcp server as well.. If your going to be setting up a AD domain - it should be dns and dhcp. If need be breakout a segment for its dhcp members.. Your other devices can continue to use pfsense as dns and dhcp. As mentioned you can setup a forwarder on pfsense for your non AD devices can resolve stuff in your AD doman.
-
Thanks, how do I set up a forwarder to my AD DC in pfSense? The DC is called boron.duc.loc at IP 10.0.0.5
-
Do I just add it in here?
-
In DNS Forwarder, Domain Overrides section. Add a domain override for "duck.loc" to go to the address 10.0.0.5 - then requests for any names under "duck.loc" will be sent to the DNS that is hopefully listening on 10.0.0.5
-
In DNS Forwarder, Domain Overrides section. Add a domain override for "duck.loc" to go to the address 10.0.0.5 - then requests for any names under "duck.loc" will be sent to the DNS that is hopefully listening on 10.0.0.5
Thanks, it's working great now.
