Exchange 2013 is using internal interface for resolving external DNS names in case of multi NIC Windows 2012 R2 server

Hi

I have deployed a single MBX Exchange 2013 server (MBX & CAS) with two NICs.

Internal NIC facing ADDC /intranet and DMZ NIC facing Firewall/SNAT and Internet.

There is a static routing configuration in place making sure 0.0.0.0/0 goes via DMZ NIC GW.

I have an access to I-net using IE and I can successfully resolve gmail.com  i.e. ping gmail.com works.

I did manual configuration for Servers>DNS lookups, pointing External DNS lookups to my DMZ NIC and Internal DNS Lookups to my Internal NIC.

In addition I have manually set Transport Service DNSs settings using Set-TransportService  cmd-let

At the end I restarted both MSExchangeTransport & MSExchangeFrontEndTransport.

Nevertheless problem remains - Exchange keep sending DNS queries for gmail.com to my Internal DNS (used only for AD) and because of that DNS lookup fails.

Am I missing something here?

BR

Plamen

June 17th, 2015 6:06am
I recommend using internal DNS for all queries and let your internal DNS resolve the names using root hints.
Free Windows Admin Tool Kit Click here and download it now
June 21st, 2015 1:37pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics