Matthew B
asked on
Mask domain on different web hosts
Ok so im trying to understand how i can mask my domain name across different web hosts.
So my setup is as follows:
Godaddy hosts my domain name: example.com
Example.com name servers are set to digital ocean
example.com website is hosted on digital ocean
My app for example.com is hosted on azure at example.azurewebsites.net
I want to create some links from example.com to example.azurewebsites.net but mask the domain name so users dont think they are leaving example.com
Is this possible? I assume i need to do something with DNS records and then something on the webserver for example.azurewebsites.net ?
So my setup is as follows:
Godaddy hosts my domain name: example.com
Example.com name servers are set to digital ocean
example.com website is hosted on digital ocean
My app for example.com is hosted on azure at example.azurewebsites.net
I want to create some links from example.com to example.azurewebsites.net but mask the domain name so users dont think they are leaving example.com
Is this possible? I assume i need to do something with DNS records and then something on the webserver for example.azurewebsites.net ?
Why not use azure.example.com and have the webserver forward the request to the other side (as a proxy) in that way you can hid the use of azurewebsites.
If you have a static IP with azurewebsites then you can use aa A or AAAA record to reach them. in the form of app.exmple.com.
If no static IP is available, app.example.com can be a CNAME to example.azurewebsites.com. .
Anyway from the IP address it can be inferred where a website is hosted anyway, from A CNAME the name is more obvious.
Is that a problem... with cloudflare you can't do it any other way . You assign the readable name to a Cloudflare name which is rather hard to read. in the form of some-cloudflare-id.cloudfl are.net that runs a proxy / filter wich will hide your real server. (another way to hide the location of your server).
If you have a static IP with azurewebsites then you can use aa A or AAAA record to reach them. in the form of app.exmple.com.
If no static IP is available, app.example.com can be a CNAME to example.azurewebsites.com.
Anyway from the IP address it can be inferred where a website is hosted anyway, from A CNAME the name is more obvious.
Is that a problem... with cloudflare you can't do it any other way . You assign the readable name to a Cloudflare name which is rather hard to read. in the form of some-cloudflare-id.cloudfl
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
From what you describe, you'll just simple DNS entries.
example.com will live at Digital Ocean.
example.azurewebsites.net will live at Azure.
Then on example.com you'll have .htaccess or Apache config directives to redirect as desired.
To accomplishing accessing example.azurewebsites.net have your App run as an API + just call this site to fetch data.
Using behind the scenes API calls is the only way to 100% hide what you're doing. Any other approach can easily be seen in any browser's debug console.