Adding a new domain controller to our network


Adding a new domain controller to our network

Hi everyone,

We just upgrade to a new MX100 form a MX80, we have a few VLANs working and we adding a new server to act as an AD domain controller, we are using Meraki as a DHCP and DNS server, trying to keep it simple, under DHCP options we add the IP of the AD Server so they can be add it to the domain, but the problems is that the network slows down and the credit card machines can not communicate outside the network, has anyone have any suggestions.


Kind of a big deal

I assume you mean you have added the AD controller as a DNS server under DHCP.


I would try running a DNS query against the AD controller and make sure it can resolve queries properly.

Under DHCP Tab DNS nameservers, Custom nameservers I add the AD IP and Merki IP local IP. It works but the network slows down and credit card machine won't communicate

Kind of a big deal

Test the AD controller directly.  From a CMD prompt go:



server <ip address of AD controller>


Does repsond in a reasonable period of time?

Head in the Cloud


I understand MX do not offer DNS Services Adding MX Local IP in  DHCP NS List shall not be of any help.

Hope your AD DNS server is working good to resolve domains. 


You may follow @PhilipDAth instructions on this.


Also consider  verifying L3  L7 Content Filtering Traffic Shaping rules and Firmware version.

Kind of a big deal

Did the slow down happen after you added the MX100, or after you added the AD controller? Which one of the two changes resulted in the slow down?

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.