Windows Forum

Ask something
Discussion Locked

DNS issue?

0 helpful
5 replies

by it1

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I just set up for our company, OWA using SSL. Our Exchange server sits behind the firewall and its address is translated at the firewall. I installed OWA on the Exchange server and put an entry in our ISP's DNS tables to point to the external IP address. Everything works ok. We also have an internal DNS server for our users to access the web from inside. I've also included host names and PTR records for the servers we have in our network. We want to customize the default logon page for OWA and our developer wants to use the URL to test it. The problem is that when the URL is typed in the browser the request times out, even though I can see that it translated to the correct IP address. So, I'm thinking that internally we can point to the internal ip address of the exchange server but I haven't been able to succeed with that. Basically I've been playing with CNAME records. Any ideas? Thanks

5 replies

by barry hensley

You will need to configure your internal DNS to provide clients with the OFF-NET address of your internal hosts. Many NAT configurations will fail if you are attempting to access an internal resource using its external address.

Also, make sure that all of the clients are using your internal DNS as their primary DNS so that host names will always resolve to the internal IP address.

by emanon

Try to create a new zone in DNS (in LAN). The zone should be the same as domain name as the DNS is ISP. Then just create the hostname in domain but with the LAN IP (instead of the global IP, which is defined in ISP's DNS).

This is because the IPdefined in ISP's DNS is actually an NAT IP. When you access from the LAN, it should refer the LAN IP.

This discussion is closed to new replies.