Web redirect

Greetings,

I am currently using Homestead to host a website that I previously had setup at GoDaddy. When I had it setup on Godaddy, I had a redirect for employees to go to our OWA mail server by visiting webmail.ourwebsite.com. I believe this was done by creating an A record that points users visiting webmail.ourwebsite.com to the IP address of the exchange server. For some reason or another this is not working at the new hosting service. What am I missing?

Thanks in advance for any direction you can provide in answering this question.
klampoAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

strungCommented:
Have you allowed 24 hours for the DNS changes to propogate?
activematxCommented:
Yes you are absolutely correct.  Login into your HomeStead control panel and create a new A-Record that points webmail.ourserver.com to the IP or dns name of your new website.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
klampoAuthor Commented:
To answer your question, Strung, yes. Yet I am noticing it working in little than under 20 minutes. Unfortunately the URL I am redirecting to is https// and it is stripping off the https:// and keeping the rest. For example. If said webaddress is https://ex.exchangeserver.com/owa it is instead redirecting to ex.exchangeserver.com/owa.

I notice the redirect is working, but the URL is not fully propagating during the redirect.
activematxCommented:
You should have your SSL url force SSL so that users will always have secure location.  If setup properly the HTTPS should enable itself even if the user is directed to http
klampoAuthor Commented:
Ok.. so here is the solution. It is a work around. I created a tinyurl converting the https:// to a regular http. Then I created a subdomain that redirects to that URL.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Email Clients

From novice to tech pro — start learning today.