I have a mail server that sits in a DMZ at one branch location. We have mobile users that have their mail programs setup to go to mail.mycompany.com. But when they are
inside the branch that houses the email server it wouldn't work. This was because I didn't have a DNS record setup for mail.mycompany.com. So I set up that record which made it work.
My issue is that we have a VPN tunnel between corp and the branch offices. So when the mobile users move from the branch office that has the mail server to another office
the DNS record doesn’t work. Because the tunnel does not allow users to see the DMZ where the email server is from the other offices. But it is all under the same domain just different subnets.
I do have all the stores on their own subnets. So is there a way to have the record for Mail.mycompany.com point to the DMZ IP at the branch the mail server is located
at. But have mail.mycompany.com at all other branches aim toward the WAN IP address of the mail server?
>Because the tunnel does not allow users to see the DMZ where the email server is from the other offices. But it is all under the same domain just different subnets.
If in this case, this means users who work at corp network will unable to access it through internal network (VPN) but form internet , I assume this domain (mail.mycompany.com) is an internet valid domain name that can be resolved by every internet
publish DNS server . So in this case, why we still need to configure internal name resolution ? By the way , are we using same internal and external domain name ?