Im not very keen on DNS configuration. Here's my issue I'm trying to configure my exchange to use (mail.swr1online.com) for my OWA url. The server name matches url. I configured the home directory to use a redirection to a URL then typed/exchange in the redirect box. I created an A Record on my hosted Domain from GodaddyHost:mail.swr1online.com points to:71.170.83.99 I only have Forward lookup configured on my DNS server. Do I need to configurea reverse lookup zone? Like I said I know little on DNS!!!!! I am able to get to owa by typing the public IP address I have NAT'ed. I tried nslookup for mail.swr1online.com and itfailed. Any ideas? Thanks guys.....!!!!

When did you set up this forwarding? Sometimes it takes internet DNS up to 48 hours to propigate changes. I don't get 71.170.83.99 i get >ping mail.swr1online.com Pinging pop.where.secureserver.net [64.202.165.92] with 32 bytes of data:Reply from 64.202.165.92: bytes=32 time=77ms TTL=109 Maybe the secure server feature is interfering with your route?

Here's my configuration. I have one win2K server that has IIS,DNS,Active Directory and exchange on it. Whenever I promoted it to a domain controller it automaticly configured DNS forwarder. That's the only DNS configuration I have. I am able to access the OWA on the server by typing "mail.swr1online.com" in the URL. I cant access it on my workstation. Like it cant resolve the name "mail.swr1online.com". Is there any additional DNS configuration I need to do?

Hi Jkurz, It sounds like your internal DNS servers are not aware of this server. You can resolve this by creating an A record on your internal zones pointing to the IP address of the server. Also depending on your network configuration you may need to point to an internal IP address if you are doing any sort of NAT on the firewall, since your traffic originates inside the network it will not travel through the firewall and have the opportunity to be NAT'd. -matt

Make sure your workstation is pointing to an internal DNS server and not the router ip or external DNS as well as checking your A records.

Here's a little more on my issue. I can get to OWA from inside the network by typing http://mail/exchange and https://mail/exchangeif I am on the server itself and I type http:// or https://mail.swr1online.com it will go to OWA. It wont on any other workstaion inside the network. Only way I can access OWA outside the network is by typing the public IP I have NAT'ed.? IPaddress/exchange I did the IIS redirection. Nothing from outside the network with http: or https://mail.swr1online.com servername is mail, but the full computer name is mail.swr1online.com

Matthew Mattoon Creating an A record on my internal DNS and pointing it to what server? the godaddy server, DNS???? I've already created an A record on my hosted domain through godaddy.

Hi JKurz,If you cannot access the server by the name from external then you will need to ensure that you have an A record on your External DNS solution (sometimes this is hosted by your ISP/Registrar, sometimes they just point to one of yours). See what your OWA is pointed to, then see what your ISP is using. The A record is the record on a DNS Server that resolves a name to an IP address. So if you are having issues resolving the IP from a name, then the A record is suspect. Now I looked at your external DNS records, since you gave the real names, and your problem is external. Basically the way you are setup is with an Alias (also called a CNAME record).DNS Servers for swr1online.comns46.domaincontrol.comns45.domaincontrol.comon these two servers you should create an A record pointing to the External IP address of the OWA server. This might be the external interface of the firewall assuming that you have some NAT/Port Forwarding Rules in place.Where does your OWA server live on your network, how would traffic get to it from the outside?-matt

My exchange server is installed on my domain controller behind a firewall. I have a static public nat'ed to my exchange. I have opened up SSL and http through to exchange on the firewall. Also did I mention I am able to access OWA from outside the network by just typing the public IP I have NAT'ed to my exchange server.

Here is the deal. Your external DNS server thinks that mail.swr1online.com is at 72.167.82.11, this is because there is not an A record. This could be related to DNS latency. Basically it can take a day or so to update, however I think most likely you are updating it in the wrong place. The DNS servers that need to be updated are: NS45.DOMAINCONTROL.COM NS46.DOMAINCONTROL.COM You need an A record pointed to 71.170.83.99, personally I wouldn't use mail (since it is most likely used for inbound mail flow) I would use owa or email or wm. Just create a new A record that is the quickest fix. -matt

OK. I had created an A Record on the godaddy side 2 weeks ago. They have a total DNS control panel where you can add A records/CNAMES (Aliases)/MX records and so on. I added mail.swr1online.com as an A record and pointed it to 71.170.83.99 which is my NAT'ed IP to exchange. This is what you are asking me to do correct? If so I have done that, and this is my issue. ? Thanks for the replys!!

I was looking over all the settings on my DNS control panel for godaddy, and there was some weird Domain Forwarder turned on forwarding the swr1online domain to another domain name I had purchased awhile back. I turned it off and, I was able to resolve owa.swr1online.com to the public static. Still is'ent working though. I will try again in the A.M. Thanks!

That was it! That stupid domain forwarder was turned on for some reason! I was racking my brain all this time! Matt - Thanks for the help buddy, I was thinking I was losing my mind! -Jon