http redirect....or..some version of...

[YeOldeStonecat]

I'm as clueless as a rusty doorknob when it comes to web server stuff. This is a task I need to do for my wife. She has a domain, let's called it "herrealtorname.com". (not the real domain). For years she's had her own website at www.herrealtorname.com...and whenever she has a new website put up, I just point the old WWW (and ftp and * records) to that IP. But those are A records which only point an IP.

She's been working under EXP now, and with their tool set, they provide a website for your now, under their domain. So https://<yourname>.exprealty.com

What I'm tasked to do is have https://www.herrealtorname.com point browsers to https://hername.exprealty.com

DNS is at LiquidWeb
I'm pretty sure things don't work if you create a CName for www and point it to hername.exprealty.com

 

[YeOldeStonecat]

I think I found out how....I faintly remember doing this years ago when she worked under ReMax. I found an old chat log that I saved, and there's an .htaccess file you can edit under the default website for a domain at a host. So at LiquidWeb, under CloudSites, I entered

Redirect 301 / https://hername/exprealty.com/

So I'll point her domains name servers to LiquidWebs...and under DNS there for her domain, update those records. Right now her nameservers/DNS records are managed by her current website people that do a lot of Realtor websites. But I have the domain registrar for her domain so I'll point that back to our account at LiquidWeb.

 

[Sky-Knight]

That's the way to have the webserver do it. I'm on Godaddy and they do free redirection with registered domains so I usually use that instead to free up the web server.

 

[glricht]

Rather than playing with DNS and other technical items that can change over time and hosts, you can also have the redirection as part of the old site's home page. Include the following record into the old site's home page (often "index.html" but could be anything):

<meta http-equiv="refresh" content="0 ; url=https://hername.exprealty.com"/>

For more info, do a Google search on "html redirect"

HTH

 

[Markverhyden]

If, literally, all you want is the website redirected then I'd prefer the route @glicht mentioned. But if there's stuff still being accessed/used at the old website then cname is the way to go. After all that's how it's done with M365 Exchange.

 

[YeOldeStonecat]

So I cutover the name servers today.
Within 15 minutes or so, trying to browse to her website, Chrome halts .."This site can't provide a secure connection"..."uses an unsupported protocol".

I run a ping to www her domain...replies to the host at LiquidWeb where the .HTACCESS file is.
It will not continue to the EXP hosted site.
Going right to the <hername>.exprealty.com is nice and secure. So the redirect is blowing up.
I can't forward her whole domain, as I have her on 365...so all those records are in place under LiquidWebs DNS.

 

[YeOldeStonecat]

Rather than playing with DNS and other technical items that can change over time and hosts, you can also have the redirection as part of the old site's home page. Include the following record into the old site's home page (often "index.html" but could be anything):

For more info, do a Google search on "html redirect"

HTH

The old site will be cancelled at the host...they're a service that's an expensive monthly she no longer needs, gone.

 

[YeOldeStonecat]

So in talking with LiquidWeb support, my unsupported security protocol error was due to no SSL on her "default" website at LiquidWeb that I'm using to do the redirect. Even though her website is not hosted there, and it's just using the default local website there for the HTAccess file to do the redirect, it still wants an SSL there.

So I temporarily flipped it over to the old CNAME approach for the time being. ...which gives yet a different SSL error. So I gotta rush and get that LetsEncrypt done for the LiquidWeb site.

 

[YeOldeStonecat]

Didn't bother with the LetsEncrypt, just purchased one...now it's working.