Re: Pointing to our new website, not our SBS
- From: CozmiqMan <CozmiqMan@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 12 Feb 2008 18:55:01 -0800
I apologize for the confusion. Let me explain again more explicitly.
We currently have an SBS 2003 Pre. Ed. that is fully recognized on the
Internet since our public DNS records are properly configured via DYNDNS (or
hairdresser). That is, currently our address is
'https://www.company.com/remote', for our RWW users (‘/exchange’ for our OWA
users), and our emails are set properly as 'user@xxxxxxxxxxx'. All works
well as expected. However, our website url still refers to an old company
name (company was acquired), whose url is properly listed as
'http://www.abc.com'. We would like to retain this website so that our
clients do not get confused with the company name; they don't understand why
the website domain differs from our email domain, it does not look
professional and its confusing and disorganized. My question is this; is
there a way to change our website url so that it reflects the proper company
name (ie. 'http://www.company.com/'), but still points to the proper website
which has a different ip address from our SBS? The only thing I can think of
is if we host the website on our LAN which is not very secure. Any thought
would be appreciated.
Thank you for your time.
--
CozmiqMan
"Lanwench [MVP - Exchange]" wrote:
CozmiqMan <CozmiqMan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:.
Hello,
We currently have an SBS 2003 Premium edition setup under domain
'xyz.company.com' on server alpha (FQDN: alpha.xyz.company.com). To
have access to OWA the public address is
https://www.company.com/remote. We have a website being hosted by a
3rd party under a different domain name (http://www.abc.com), but we
need to have it point to our current domain name 'www.company.com' or
'company.com'; however still hosted by a 3rd party (I know it's not
wise to host it on our SBS...got it). How can I go about doing this
without having the public point to our server as opposed to our
website (different IP address) ? Our DNS setup is configured via
DYNDNS.
Thank you for your help.
I don't understand the problem. You've got a public domain name
(company.com) which does not match your internal AD domain name
(xyz.company.com).
The DNS for company.com must be handled by an outside DNS hosting company or
your ISP or your registrar (this is between you and your hairdresser). You
need to have them set up an A record - a host on the company.com domain,
which points at the correct public IP. This should be the same IP address
currently used by www.abc.com , wherever that is being hosted.
Your internal DNS will only attempt to resolve hosts on the xyz.company.com
network. If you type www.company.com into your browser, your internal AD
should hand the request over to the forwarders you confgured in your DNS
server when you ran the CEICW (or will use root hints). Same with
foo.company.com or www.google.com.
You don't do any of this on your LAN.
Hope this helps.
- References:
- Re: Pointing to our new website, not our SBS
- From: Lanwench [MVP - Exchange]
- Re: Pointing to our new website, not our SBS
- Prev by Date: Re: Help! w/ Upgrade-Installation problems with OMA/ActiveSync and
- Next by Date: Re: ntbackup incremental fails First Storage Group access error
- Previous by thread: Re: Pointing to our new website, not our SBS
- Next by thread: Re: Pointing to our new website, not our SBS
- Index(es):
Relevant Pages
|