Enabling Domain Access on localhost

One way to do it is to tell your local 'hosts' file where to direct the 127.0.0.1 local address.

I run a testing server on OS X, and have the following in my etc/hosts file:

127.0.0.1	localhost
127.0.0.1 example.com
127.0.0.1 one.example.com
127.0.0.1 two.example.com
127.0.0.1 three.example.com
127.0.0.1 ken.example.com
127.0.0.1 www.example.com
127.0.0.1 www.one.example.com

Which lets me do testing on the local machine. You can also set up Virtual Hosts through Apache, I believe. But editing hosts works fine for me.

No idea.

This should be something you can find out in the WAMP server documentation or with a quick Google search. I just do not use Windows, so cannot answer the question.

It should be the file "lmhosts" file. More info here:
http://en.wikipedia.org/wiki/LMHOSTS

In response to #10, I'd suggest you don't include slashes in domain names (but dots are ok). This will likely work better:

127.0.0.1 localhost
127.0.0.1 lab.localhost
127.0.0.1 lab2.localhost

As for mistyping when you enter primary domain name (#11) - that is a problem. Though you really don't need to delete and start over. You can add the typo to lmhosts too (that way the form updating the primary will have effect - afterwards you can delete the typo from lmhosts), or you can change the "domain_root" entry in the {variable} table. Both are less work than reinstalling.

If you change 'domain_root' in the {variable} table, you will also need to empty the {cache} table -- or at least drop the 'variables' row from that table.

Tip:

And to call your live domain you just type http://www.mydomain.com
And for your local domain you type http://mydomain.com

works good for me :-)

hi nirvana jyothi
iam trying to install domain access
in mylocalhost etc/hosts

127.0.0.1 localhost
127.0.0.1 newone.localhost
127.0.0.1 web.localhost

creating domain record i gave newone.localhost if i click on domain view link iam getting page not found
can u help me before creating sub domain any folders to create in main domain folder or any settings
where to place my settings.php for sub domain
please tell me
iam searching for this since 15 days

thanks for ur reply
i created domain record but if i click one.localhost.com it is redirected to blankpage

http://one.localhost.com/newproject/admin/build/domain/view

no view created with my domain access module

if i edit domain record this meessage displayed

http://one.localhost.com/newproject/ is not responding and may not be configured correctly at the server level. Server code 404 was returned.

Configured and it worked, thanks to everyone in this thread. But I get Access denied when I enter Admin pages for that subdomain. Do I have to assign user 1 for every subdomain?
P.S. Fixed. Just logged in as user1 in that sub. Can't believe it's working)
P.P.S Edited settings.php to add dot before example.com at cookie domain.

Wampserver has my local site url as localhost/site-name, example localhost/estates
If I want something like Newyork.estates.com and Lasvegas.estates.com, how do I configure the subdomains?

Thanks.

Using Acquia's Dev Desktop for local Windows development, I was also able to set up Domain Access successfully on localhost by editing the hosts file at C:\WINDOWS\system32\drivers\etc\ as described above.

One additional step was necessary in my case in order to prevent a new database setup for the additional subdomain: editing the vhosts.conf file.

Here's the procedure:

1. Open the file located at: C:\Program Files\acquia-drupal\apache\conf\vhosts.conf
2. Copy the entire virtual host entry for the site on which Domain Access is installed (all text from <VirtualHost *> through </VirtualHost>), and paste it at the bottom of the file.
3. Change the second line of the new entry from e.g. ServerName localhost to ServerName newsite.localhost

Once Dev Desktop's Acquia Drupal stack had been stopped and restarted, the new subdomain functioned normally.

(Note: I am using a Drupal/DA 7.x, but basic setup appears to be the same.)

@Izimmerman
Can you post the code you added in the hosts file? as Acquia uses localhost:(portnumber) i am still struggeling to find the correct configuration...

@drupalok
Absolutely. Here's the updated hosts file:
127.0.0.1 localhost
127.0.0.1 site.localhost
127.0.0.1 site2.site.localhost

The second entry is actually the primary domain, since Acquia Dev Desktop already uses subdomains to distinguish sites. The third entry is a new Domain Access domain, with an extra subdomain as a prefix.

I didn't need to add the Acquia port in the hosts list, but added it to the domains in Drupal:

site.localhost:8082 (Default Domain)
site2.site.localhost:8082 (Second domain)

I also added a new entry to vhosts.conf, copying the last in the file but changing the server name to the new domain (e.g. site2.site.localhost) and restarted the Acquia stack. This step prevented Acquia from trying to create a brand-new Drupal installation at the new subdomain.

I haven't done complex work with this setup, but I have verified it for the purposes of testing themes and publishing content to different domains.

The much better way to do local testing IMHO is creating an alias domain. The /etc/hosts file (& similar hosts file on different OSes) have a problem: you have to hack with the domains and can never be sure if you are on the local site or the live one.

I solved the problem this way: enable the "domain alias" module, and create for your domain "example.com" an alias named "example.local". Then all you have to do is add "127.0.0.1 example.local" to your hosts file, enable the (LAMP/WAMPP/XAMPP) web server config and you're done.

Additionally I add some code into my custom modules to check if the current IP address is "127.0.0.1", and if yes, drupal_add_css a testing.css file, which contains a body {background: red;} tag. So I know instantly that I am on my local site if my background is red.

And the domain alias way is much cleaner and doesn't need to make me change my hosts file each time.

Just my 2 cents.