LAN client computers ping remote.mydomain.com and it resolves to our static, WAN IP Address. It should resolve to our server's local LAN IP Address.
The Details: We have a total of one server which is running SBS 2008 on some pretty fast hardware (can describe it if necessary). I've entered some local DNS zone A records so that users can use Outlook Web Access seamlessly whether they are on the LAN or outside the LAN. These DNS records include remote.mydomain.com and outlook.mydomain.com. Two domains is not necessary but the latter is easier for users to remember when accessing OWA.
I've also configured our SBS 2008 DHCP Server so that client computers get three DNS server IP Addresses as follows:
192.168.1.10 (our SBS server) 184.108.40.206 (OpenDNS) 220.127.116.11 (OpenDNS)
The reason I have it configured this way is so that clients will still be able to access the Internet in the rare event that our server is not operational.
I think the problem is that that SBS 2008 doesn't respond quite fast enough to DNS queries so the clients go on to query OpenDNS instead, which hands back an address that is only correct if they are outside the LAN.
FYI, we are using a SonicWall TZ-210 router.
I'm looking for any suggestions on how I might ensure that LAN client computers can access OWA on our LAN without having do disable the "backup" DNS server addresses that I've configured via DHCP.