Trade-war shortcuts and FBA are a good idea here if you think you need to. This is to prevent your users from accessing the site with an IP not coming from the same location as the host you’re using to host the page (and thus, the redirects) So, it’s possible to build a page in HTML on your own server. You could then use your FBA to create the redirects and your CNAME to redirect users to that page. But if you decide later to host the page on a different IP, you will need to make sure that your redirection system continues to work. By configuring your web server to only accept requests coming from the same IP that was used when the page was first requested, you can avoid redirection loops. If you have a static page you want users to access directly from a different hostname, this is also possible. If it’s just a normal website that uses PHP and MySQL, your URLs need to change. As I said, this is because you can only use the same IP address once to access your site, so if your users use the same IP to view the site as another user (and then redirect the second user back to your page), the first person will get an error message. If your users access your site through a web browser, this will not pose a problem, but if you have a native app (e.g., a Windows desktop application, a BlackBerry mobile app, a Flash site that plays audio/video), you’re probably stuck redirecting the user to a new URL. This is because browsers have their own cache to store your cookies and other browser-specific stuff (a “cookie”, if you haven’t heard of it, is what a web browser gives you when you use it to log in to a site). When a user makes an app request, your web server will only see an IP address, not a URL. When you redirect a user with the FBA and CNAME system, and the second user’s web browser sends an app request to your web server, it will know that there is a redirect path. The server will not be able to see a URL, only an IP. This will force the browser to ask the web server for the site, which in turn will redirect the user to the URL that you sent it. Now, the third user uses the same browser as the first user, and the same thing happens, and so on. If this happens, it may cause a problem with your user base. I don’t want to have to use an intermediary. I want users to be able to access the site from their own domains. For example, I have a website with some text on it. There’s a link that says “To Download the .zip file”, so if someone tries to access the .zip file by entering http://www.mysite.com/index.zip, I want them to be redirected to http://www.mysite.com/. If I do this with a CNAME, visitors will get an error message because the page is not found on that host. If I don’t do it, but instead use an FBA, the users will get redirected to the .zip file, but they will still get a 404 error when they try to open it. This is because the FBA does not check if a particular IP address is allowed to access the site. If you enter my site’s IP address in your browser, you’ll get a prompt that says “The web page from this server does not exist,” but when a user comes from an FBA address, the web server will not perform that check. The only solution here is to set up your web server to use another IP address for your redirects. The only time I can think of this happening is if you go from example1.com to example2.com, and you don’t redirect. The browser then automatically redirects to example1.com and it gets the HTML or what have you. This is why you need to have a redirect from example1.com to example2.com and you should be done here. The problem with using different ports is that users will not know they’ve been redirected. When you change the URL to point to port 90, the user will get an error because your URL is still pointing to port 80. For example, http://www.example.com would be redirected to http://www.example.com:90, and a request for http://www.example.com/index.php would be redirected to http://www.example.com:90/index.php. This is because of a browser cache issue. To redirect properly, you would have to do something like this: http://www.example.com:90 and if you didn’t want the user to see it in the URL, you would redirect to http://www.example.com. This is the result of FBA not knowing that there’s a redirect to another site. For example, your FBA is a WordPress blog. This blog uses a CNAME, but also has a redirect on the domain. People are redirected to the blog’s main page, and then your CNAME redirects them to the WP login page. If someone tries to go to the login page, it won’t load because their browser thinks they’re still at your site. If your web server is on a Linux server (Ubuntu, Fedora, etc.), I recommend you use the nginx webserver. nginx is very lightweight and is very useful when you need to use Apache for other things, but you need to create redirects. I’ve seen people using apache on Windows with no problems, but I’ve found that sometimes there’s too much of a performance cost if you use apache. There’s an apache module called mod_rewrite, which is what allows you to redirect from the URL, but you have to compile apache separately if you don’t already have it. I’m guessing here that you’re a Windows user. On Linux, I would suggest installing and setting up nginx. To find the IP address, just look at your Apache error_log file. It will be printed there when the user visits your site and attempts to access it via IP address. In the example above, the IP address that is given in this message is not a valid IP address. Instead, it is given the IP address of the proxy server (127.0.0.1). The correct way to fix this issue is to assign the actual IP address of your web server to the proxy server. This allows you to have URLs that users can type without having to enter a local IP address, like they would if they entered http://localhost. You can also try setting up your CNAME to point to a different IP address, or even just a different subdomain of your main site. The IP address of the web server (i.e., your public IP address) is http://www.ipchicken.com, so if you’re trying to access a file by accessing the IP address, this won’t work because you need to provide an IP address to use in the URL. This doesn’t mean you need to delete the index.php in all the directories on your server (such as /var/www/html). You need to delete the index.php in those directories only that are accessed through your main domain (www.example.com). If you used a subdomain, like www.example.com/blog, you would only need to change the configuration of that particular subdomain. However, if the main domain (www.example.com) and the subdomain (www.example.com/blog) both use index.php to access the main site’s content, you will have a problem. In this case, you need to fix this problem by configuring your web server (Apache/nginx) so that the web server knows not to try and find index.php in the non-subdomain folders, and instead just send a 403 Forbidden error. I recommend you try to configure your web server so that it looks for index.php (or whatever name you want) only in the folders that are accessed through your main domain (www.example.com). I don’t want to use a redirect, I just want to have a page that can be accessed from http://example.com/mysite1/ Your example URL for accessing the sub-page (in this case, www.example.com/mysite1/). It is not an example of an IP