Probably a dumb question.....

[CBack85]

I have an external domain mail.mycompany.com that works great for OWA and Activesync on Android and Apple devices when you are not in the office.

When in the office though I can't figure out how to get that same domain mail.mycompany.com to resolve. The devices just error out and can't connect that way. Is there an easy way to fix this in DNS I am assuming?

 

[Noway2]

Not a dumb question at all. Working outside of your office says that the global DNS system has your site properly resolving. Normally, I would think that your office's DNS would recursively try to resolve the address. The exception would be if it thinks that it is authoritative for the domain, in which case it looks like it doesn't have an entry for the host. If your office DNS is authoritative for the zone, I would look at the zone record very carefully.

 

[cajuntank]

Setup what's called a split-DNS system. You create a zone internally that matches the names that you have for your external DNS, but just make the records resolve to the internal IP addresses of the servers. Be mindfully that once you create this zone for internal use, you will need to have records defined for all hosts needed as the external DNS will not be used to resolve hosts for a zone that already exists internally.

Doing this way, you can define all of your URLs the same in Exchange for OWA as they will resolve to either the public address or internal address depending on which side of the network you are on.

 

[CBack85]

even if my domain is .local on our internal server can I still setup "Split DNS"?

 

[CBack85]

ha awesome got it figured out!

thank you very much guys!

 

[GlenJohnson]

And the answer is?

You gotta share dude.




Be civil to all; sociable to many; familiar with few; friend to one; enemy to none.
Benjamin Franklin