I have a drupal site where I use the domain access module that works using inbound HTTP_HOST variable.I have to create some subdomain's also.To make this module work properly the $_SERVER['HTTP_HOST'] variable should have the domain name in it .But I am getting the ip address of our server.So my site is not working properly.I am getting the main site.But the subdomains are not working.All are pointing to the main site.
My site is on our server and we asked our host to point our domain name to 172.XX.XXX/drupal.Our subdomains are also pointed to 172.XX.XXX/drupal.
So when I type the domain name it is showing the site but the http_host has IP in it.We have a VPS host plan.What should I do to make it work properly.
Please help.
Thing looks very easy.
You are just required to tell your domain host provider to point all your sub - domains to 172.xxx. ip / drupal.
some examples.
a.yourdomain.com => actuall would point to 172.xxx/drupal.
b.yourdomain.com => actuall would point to 172.xxx/drupal.
c.yourdomain.com => actuall would point to 172.xxx/drupal.
After that your domain access module would automatically take care of your sub-domain wise access to content.
Note: Technically domain access module would show the content based on your current sub domain name.
Related
Hi is it possible to stealth redirect a domain to another domain and in the meanwhile keeping the url of the first domain visible in the address bar?
Using cPanel and able to edit htaccess
I am not sure that this is possible, but you can instead do the following:
Use iframe in order to display the destination website inside your current website in "full screen". Read this for more information.
Point your domain name to the ip of the destination. This might not work if the destination uses virtual host, but you can try. Try using the same the sub-domain if this doesn't work.
I have many domains with different extensions, for example: website.com, website.net, website.org,...
the main site/domain is website.com where I have installed WORDPRESS
what I'm tring to do is to set all the others domain (website.net, website.org,..) to point on the main site/domain (website.com)
so, for example, if I go on "website.net" or "website.net/something" should I be redirect on website.com
I have cpanel so i guess that the first way is to add all the domains with the "addon domains" function, and then add in the wp-config.php:
define( 'NOBLOGREDIRECT', 'http://website.com' );
or another soluzion could probably be to simply park all the domains with cpanel function, or se the htaccess, but how?
what is the best solution in this case?
PS: the main website is in a subfolder (not root)
Just do a DNS forward and be done with it. Go to your DNS provider and just setup domain forwarding to your main domain name.
Forward website.net and website.org to website.com. When anyone goes to website.net it will redirect to website.com and same with .org. The domains will need to be parked.
If you host your DNS at a registrar like GoDaddy, then this will show you how.
http://support.godaddy.com/help/article/422/forwarding-or-masking-your-domain-name
Otherwise, the procedure is the same wherever your DNS is hosted. I suggest forwarding it without masking.
I'm hosting a clients site at client.mysite.com, but my client want to have its own domain, like www.clientsite.com.
With a CNAME configuration, I'll be able to hook my client domain to the content, but... considering I'm still hosting my clients content, which domain will be finally listed on Google with contents of client.mysite.com contents?
a) mysite.com
b) clientsite.com
Thanks for helping.
In the DNS hierarchy, the CNAME resource record will be attached to the clientside.com. A CNAME is simply a reference to the location of that site's A record. With that in mind, I believe mysite.com will be listed as hosting the data.
Does your client want it to appear under his name?
If so, then this should not be solved using DNS (well, not only using DNS).
If your client wants to get the content listed under his domain name, the best way to do this, is to add their name to your server.
Then point client domain name to your server.
The best way to do the pointing (when also considering SEO)
is to make an webforward (301 permanent) from the root, to the www
and make the www subdomain point to the ressource.
(Or vice verca)
IF you are using the example above (webforward on root) you can use a cname instead of an A record to point the domain name. However do not add a cname to the root of a domain (effectively shutting down your domain name).
So-
Short Answer:
client.mysite.com will have the content (also according to google).
Any attempt to obfuscate this is black hat or grey hat ;)
a better way of doing it is to simply setup the clients domain name on your server.
Then point only one hostname to the server. Server host/headers will take care of the rest.
Setup in DNS
# webforward 301 www
www a or Cname to server
Quick rules:
NEVER put Cname on the root of a domain
Only allow 1 hostname to show content (can be done both as explained above via DNS/webforward or via server configurations)
I am new to rewrite site url name. I have a site url like http://66.15.101.250/test/ . this is my owned server link So i want to change this site url to something other name like http://testsite/test/ ( i do not want to give domain name to this ip address url).And i have otheres site running on this http://66.15.101.250/test/ server . I have no idea how to do this, what should i do.
Is this possible through .htaccess file or something else
Thanks in advance
Your server can only respond to requests it receives, and will only receive requests routed to it by DNS, so if you don't own the domain name, you can't receive public traffic directed towards it. You could silently redirect users from
http://66.15.101.250/test/ to the content found at http://testsite/test/ but they would still see the http://66.15.101.250/test/ url in their browser.
If you think about it, its a good thing you can't do this or I could make stealyourcreditcardinfo.com appear as paypal.com. Indeed most uses for what you are asking about would not be legitimate ones...
For your own internal testing purposes, you can make virtual host entry for testsite.com and your server will respond to any requests it receives for testsite.com. You then change your HOSTS file to point testsite.com to 127.0.0.1 and testsite.com will work in your browser, but only on your machine because you manually overrode your own DNS. The DNS everyone else is using is still pointing testsite.com to the actual IP address somewhere else
If you need this for testing purposes (as it seems to me), you can put 66.15.101.250 testsite in your hosts file and configure a virtual host for testsite in your webserver.
Under my domain, one of the subdomain must be directed to one server that hosts the relevant applications, and the rest must be directed to another server that hosts the relavant applications.
So, any requests to the url appa.example.com\* must be directed to one server, and any requests to the url appb.example.com\* must be directed to another server.
The issue now is how to configure the Apache configuration on both servers-- maybe using configuration like ProxyPass or ProxyPassReverse so that they all the incoming requests can be directed correctly at the correct server?
Edit to make the question clearer.
The place to link an url to an IP (server) is the DNS.
For example if server A is at 1.2.3.4 and server B at 5.6.7.8 you link appa.example.com to 1.2.3.4 and appb.example.com to 5.6.7.8.
But if both servers are behind a firewall (with a single external IP address) you have to perform some tricks. (And you are probably looking for these tricks).
Have a look at An Introduction to Redirecting URLs on an Apache Server.
I've done the same thing for my workplace (a University). Our primary website it hosted elsewhere but part of the site (student registration system) is hosted onsite.
What I did was to create a Authoritative (A) DNS Record (reg.domain.com) and made it point to the IP of our onsite server. And that did the trick!!!
Here's a screenshot of the same from my domain CP (domain and IP masked for obvious reasons)...
alt text http://img443.imageshack.us/img443/5069/stiuaregrecord.jpg
It's essentially the same as what you're trying to do. Give it a shot and see :)
In the DNS records/manager for the parent domain of the intended subdomain:
point the subdomain name at the to-be host servers IP address, then ...
... Then ...
In the host server DNS and or server-software config: direct the subdomain to the website app. You can achieve this by one of: -
manually edit the DNS records,
park the subdomain and point it at the website document root folder, or
add the domain and subdomain (domain will never be used since its not pointed at applicable server). Point them both at the document root for your now subdomained (if there is such a word) website app