bootcampwithjess
asked on
Local DNS question
I have a mid size network with 100+ users and have a question about DNS. DNS is forwarded to our ISP for resolution
We have an exchange 2007 server here in our building that the users usually use OWA to access thier mail... However, OWA is routed through subdomain.domain.com/owa - so my question is: how do I place a DNS record in the server to catch any request for that subdomain.domain.com - because when I try to add a host A record is automatically completes the FQDN as subdomain.domain.com.PH.lo
I'd like to keep owa traffic internally, internal and poing it to 192.168.0.x rather than an internet ip 173.8.xx.xx
Any suggestions?
dns.jpg
We have an exchange 2007 server here in our building that the users usually use OWA to access thier mail... However, OWA is routed through subdomain.domain.com/owa - so my question is: how do I place a DNS record in the server to catch any request for that subdomain.domain.com - because when I try to add a host A record is automatically completes the FQDN as subdomain.domain.com.PH.lo
I'd like to keep owa traffic internally, internal and poing it to 192.168.0.x rather than an internet ip 173.8.xx.xx
Any suggestions?
dns.jpg
Are you running your own DNS and just forwarding to your ISP, or is your ISP providing the DNS?
Skiddy is right, unless you are not running your own DNS...
He has to be running his own DNS - he's running Active Directory.
More generally, I hear you asking this: how can I get my internal users to use IP address blah to connect to the OWA on the Exchange server.
Can you use an IP address in a URL to access the OWA? If you can and that's an OK solution, you could use a GPO to alter the E-Mail Start menu item to point to IE with that URL loaded. Or just put a shortcut on the menu or desktop.
Or use a script to do the same.
Can you use an IP address in a URL to access the OWA? If you can and that's an OK solution, you could use a GPO to alter the E-Mail Start menu item to point to IE with that URL loaded. Or just put a shortcut on the menu or desktop.
Or use a script to do the same.
ASKER
I am running DNS on my server, although it's an internal DNS and all the requests are forwarded to the ISP dns... My thinking is the SSL cert. when an internal user goes to https://subdomain.domain.com rather than go outside the network to be routed back inside, can't I subvert that and have it go straight to the exchange internally? I've tried using a direct ip setup https://192.168.0.8/owa - but then get a certificate error, then the user must click to accept the error, That's what I'm trying to avoid alltogether...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
skiddy89 - thanks for your help. My new problem is: domain.com is an actual website hosted offsite (Outside our internal network) when I add the domain.com zone, then add A Host record of subdomain.domain.com, I can hit my exchange server internally no problem. It's resolved to 192.168.0.8...
Now when I try to hit domain.com - which our users hit often the site *cannot be resolved* - the DNS does not forward that specific request for domain.com...
Suggestions???
Now when I try to hit domain.com - which our users hit often the site *cannot be resolved* - the DNS does not forward that specific request for domain.com...
Suggestions???
ASKER
Thanks for the help! I added two A host records that point to our external site under the domain.com suffix - I got an error in the process, but users can still navigate to domain.com and not have it point internally. :)
Thanks Again!
Thanks Again!
Sorry, I should have been more precise with my wording.
"anything it doesn't find it'll forward though."
I meant anything out of your internal zones - because domain.com is in your internal zone, it'll stop there if it doesn't find an A record for something.
Just add the A records that are on your external DNS system into the local domain.com zone - it takes a little while if you have a lot, but after that they're there. You'll only run into effort if you change them regularly or add new regularly.
"anything it doesn't find it'll forward though."
I meant anything out of your internal zones - because domain.com is in your internal zone, it'll stop there if it doesn't find an A record for something.
Just add the A records that are on your external DNS system into the local domain.com zone - it takes a little while if you have a lot, but after that they're there. You'll only run into effort if you change them regularly or add new regularly.
This will keep the DNS request internal as your internal DNS server will handle requests for domain.com also instead of forwarding them - anything it doesn't find it'll forward though.