Ask How can I redirect my domain without revealing all the details of my old site?

[Brajet]

Hi, probably easy question but I don't know what exactly to change. I followed this guide almost 2 years and everything has been working rock solid for all my domain (abc.com i.e) redirect from the internet. I have a few internal services that I don't want to expose to the net but still like to access with my domain from inside the network. for example, I want to type sub.abc.com. and access the internal service just like I can from outside but without adding A record to my domain in cloudflare. the best I found is to set DNS rewrite but I still need to add the port (sub.abc.com:4444) in order to access. I tried to add real and backend services but I am note sure where I set in either HAproxy or unbound that any request to sub.abc.com will redirect to 1.1.1.1:4444. Any suggestions?

Thanks!

 

[Anthony Joshua]

One simple method is to use a 301 redirect from your old domain to your new one but only for the main domain or selected pages. That way, people don't see the full structure of your old website. You can also set up a new homepage or landing page on the new domain and redirect everyone there. This lets you control what visitors see while keeping old content private.

 

[Brajet]

You can do a masked redirect. Basically, it keeps your new domain in the browser bar while showing stuff from the old site. Most hosting services or domain registrars let you set this up easily. Another simple trick is to just make a landing page on your new site with links to the important bits of the old one. That way, people get where you want them to go, but they don't get a peek behind the curtain at all the old site's URLs or structure.

 

[Felix😎]

For your setup, you can create a local DNS override in Unbound to resolve sub.abc.com internally to 1.1.1.1. Then configure HAProxy to listen on port 80 or 443 for sub.abc.com and forward traffic to 1.1.1.1:4444. This will let you access the service without typing the port. You don't need to involve Cloudflare for internal services—local DNS and HAProxy should handle this perfectly.