I have purchased a domain name on godaddy.com. I am currently able to set the domain www.xyz.com to my webserver whose url looks like:
http://11.12.13.14:8040/server_files/
I have done this by opting for link forwarding along with cloaking of the original url. This has two disadvantages:
1. When the user views source of the page, they’ll find that it is merely the original page with a frame around it with path set to
http://11.12.13.14:8040/server_files/
2. When I specify relative paths, it exposes the IP address and port and the only way to circumvent that is by hardcoding the absolute path everywhere, which I would like to avoid.
Any idea what is the correct bunch of settings that I should opt for in godaddy.com and in my server (which runs apache tomcat), in order to do this in a clean way?
Next: What Is Better, Yahoo Small Business Web Hosting & E-mail Or Godaddy?
Previous: How Can I Use My Web Server To Host Other Websites?
"How To Set A Newly Purchased Domain Name From Godaddy.com To The Ip Address Of A Webserver.?" was posted on Friday, September 18th, 2009 at 9:35 am.
what you want to do is domain forwarding, as far as i know, godaddy has this option, you should search for it.
however, this would mean that http://www.zyx.com will be http://11.12.13.14
if you forward the domain name, you will have to use http://www.xyz.com:8040/folder/ or any other path that you use on your apache webserver
so you might want to put all your files in the root of the http server, that way you don’t have to use /server_files/
and the standard port is 80, if it’s free, you should set your apache server to run on that port so that you don’t have to use the :8040 after the address
LATER EDIT:
“domain forwarding” means translating a domain url into an ip, i don’t know exactly what you did there, but there’s no way to forward a domain url to another url.
I mean, you can’t forward http://www.xyz.com to http://12.34.56.78:8040/server_files
What you can do is forward http://www.xyz.com to the IP 12.34.56.78 and then the domain name will become the same with the ip.
After the forwarding, what you could see when you were accessing http://12.34.56.78 you will also see when you access http://www.xyz.com and if you create a folder on your server (like “server_files”) then you will have http://www.zys.com/server_files/
so basicaly, the domain acts just like a mask, hiding your ip from the url but the rest of the paths (and ports) remain the same, that’s why i recommended you move the files in the root folder, to get rid of the /server_files/ extension from your url address and this is also the reason i recommended the standard 80 port.
If you use port 80 for your http server, then when you tell someone to check your webpage, you dont have to provide the port at the end of the url, so it will be clean, like http://www.xyz.com instead of http://www.xyz.com:8040
Having your files in the root (remember here we’re talking about the root folder of the http server, not your computer’s root folder) is the same as having them in the ’server_files’ folder, that is unless in the root of the http is not another website
so to make things clear, forwarding = a name for the ip and you can’t point it in any direction other than an ip. If you don’t want this then your other option would be redirect, which will show your ip in the url address
actually your options are:
1. you do the forwarding and have the url http://www.xyz.com:8040/server_files
2. you do the forwarding and change the port to 80 and move the files from the ’server_files’ folder to the root and you’ll have the url http://www.xyz.com (clean and nice)
3. you redirect in which case when someone enters http://www.zyx.com in the browser, it will take him to http://12.34.56.78:8040/server_files (and he will be able to see the ip)
4. opt for a virtual host in which case they take care of everything for you:)
sorry for the long and boring explanation