This should be a simple question to answer, I'm just not that experienced yet.
I'm in the process of setting up an Active Directory domain in an existing office network. The network previously consisted of only a dozen Windows machines and a few VoIP phones, all handled using the router's DHCP. I've added to this a Windows Server 2019 machine, which we'll call
Controller, that has been configured as the domain controller of a new domain, which we'll call
So far so good. The problem comes when I try to join machines to the domain.
When attempting to join a Windows 10 Pro machine to the domain, I get the message:
An Active Directory Domain Controller for the domain "mydomain.com" could not be contacted.
I did some ping testing:
Controller'sIP address) works.
ping Controlleralso works.
ping mydomain.comresolves to some public address, not the address of
So the problem is with DNS, it seems.
Since the network is governed by the router (DHCP and DNS), I'm assuming I need to configure the router to use
Controller as a DNS server. I'd like some guidance on how to properly do that.
The router is an Arris TG1682G. This is what the current LAN configuration page looks like:
The "?" icons provide some tool tips that might be useful:
Which settings do I need to change so that the router will try to resolve
mydomain.com internally first, using
Controller, before attempting to resolve it externally?