Hi - I am setting up a new (or rather re-configuring) network. We have been using a dell poweredge windows server 2016 as a in house development web server, but have decided to re-purpose it as a Domain / Active Directory / File Server.
Having setup the server with a static IP, configured AD, and setup some users I then tried to connect my Windows 10 client which failed. The client is set to obtain IP & DNS credentials automatically from our router. Therefore the client was obtaining a DNS which pointed to the router / gateway. Manually changing the client DNS to point to the server fixed this. But this is far from ideal.
Looking at our router there is no way to change any of the DNS info.
So my question is should our server really be acting as DHCP as well? If we do go down this route will there be any issues with all of the non domain items we connect wirelessly via the router iPhones, iPads, guest computers etc...
Most of the clients will be laptops that must connect to the domain automatically when in office but when out of office must still be able to connect to internet without any issues for technical users.
Thanks :-)