Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 231
  • Last Modified:

how to specify exchange virtual directory in public DNS

how to specify exchange virtual directory in public DNS
I would like to have internet users type:
owamail.mycompany.com in the address bar of the browser, so that they can connect to exchange via outlook web access.
how do I set up the records in public DNS?

thanks
0
jskfan
Asked:
jskfan
  • 3
  • 2
  • 2
4 Solutions
 
maxsmith5kCommented:
You need to set up a host record that resolves to the public ip of your cas server. Then you set up forwarding in iis so that anything that comes to owamail.company.com automatically forwards to owamail.company.com/owa
0
 
maxsmith5kCommented:
Just an extra point, you will probably have a firewall in the way so the host record would resolve to the firewall, which would have NAT in place to forward to the cas
Server
0
 
jskfanAuthor Commented:
can you paste an example of the public DNS records here??
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
kevinhsiehCommented:
The standard syntax is below, but you need to contact whomever provides the public DNS for mycompany.com and have them add the record.

Owamail.mycompany.com. IN A 8.8.10.25
0
 
jskfanAuthor Commented:

for instance:

A record for mycompany.com=8.8.10.25
A record for owamail.mycompany.com=9.9.9.9

MX record  @ mycompany.com

if a user sends an email to  john@mycompany.com
then anything after @ is considered as an SMTP port 25 and it will point to 8.8.10.25 and the firewall should allow port 25 and NAT the 8.8.10.25 to Exchange server ip address

and when a user types owamail.mycompany.com it will be redirected to 9.9.9.9 and the firewall will NAT it to exchange FE , assuming we have exchange 2003 only.

this is how I am understanding it.
0
 
kevinhsiehCommented:
If you are running Exchange, the MX record would normally point to something other than mycompany.com, because mycompany.com would normally resolve to the IP address of your mycompany.com web server, which is probably not your Exchange server. At an rate, if your inbound email is already being routed properly, you don't need to touch the MX records - you only need to add an A record for owamail.mycompany.com.

mycompany.com. IN MX 10 smtp.mycompany.com.
mycompany.com. IN MX 20 backup-smtp.myisp.com.
smtp.mycompany.com. IN A 8.8.10.25
owamail.mycompany.com. IN A 9.9.9.9
0
 
jskfanAuthor Commented:
thanks
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 3
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now