I have a bit of an issue with the DNS in one of the offices that I manage. I've installed a second internet connection for the users to use because the primary internet connection is used for the mail server. I have two servers both running DNS SERVER1 192.168.1.12 SERVER2 192.168.1.14 Both servers default gateways are pointed to 192.168.1.1 DHCP points the users gateway to 192.168.1.2 Both servers DNS settings point only to themselves I'm just wondering what the issue might be and how I would go about testing and resolving it.

What are the devices at 192.168.1.1 and 192.168.1.2 Would have expected all devices on 192.168.1.xxx subnet to use same gateway (router?) Make sure local DNS server has own address as primary and other DNS server address as secondary in network connection properties and is not multi-homed. Also put public DNS addresses as forwarders only on local DNS server. Client should have local DNS address only so client can find and logon to domain. Forwarders are so clients can find and resolve internet queries. Regards, Dave Patrick .... Microsoft Certified Professional Microsoft MVP [Windows] Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

192.168.1.1 & 2 are both routers and are hooked up to our local high speed provider. 192.168.1.1 used to be our only gateway but since we've added an exchange server, we were constantly having issues with internet slowdowns. We were hoping that if we routed the office users out a different internet connection, we wouldn't have the bottleneck that we appear to have with the exchange server.

Hello, please post an unedited ipconfig /all from the DC/DNS servers and the Exchange server, hopefully this is a domain member and not a DC.Best regards Meinolf Weber MVP, MCP, MCTS Microsoft MVP - Directory Services My Blog: http://msmvps.com/blogs/mweber/ Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

I will get that done today The Exchange server is a domain controller. Should it not be?

Exchange server is also a domain controller, which is not a recommended configuration. http://technet.microsoft.com/en-us/library/aa997407(v=exchg.80).aspx http://blogs.technet.com/b/omers/archive/2011/04/11/microsoft-exchange-server-on-domain-controller.aspx http://www.arabitpro.com