In a previous article, I talked about using subdomains in Rails 3. Since then, many people have elaborated on the topic. There's even been a great Railscast.

I've found Tim Pope's post particularly useful. Basically, he has set up a domain name that resolves to locahost/ This save you from having to specify subdomains in you /etc/hosts file - which is a hassle!

I'd like to offer another alternative using Dnsmasq. With Dnsmasq, you can set up a simple DNS server locally, then you can use an apache virtual host to deal with wildcard domains.

Install/Configure Dnsmasq

First, install Dnsmasq - I'm using Ubuntu (sorry for those who aren't).

Now, edit the /etc/dnsmasq.conf file:

The listen-address basically defines what IP address Dnsmasq will listen on. In our case this is your local machine.

The address line specifies a lookup for the name blah.localhost. As you can see, this is mapped to your local machine also.

Believe it or not, that's pretty much it! And if you've tried to use Bind for a similar job, you'll be very happy right now.

One more thing though! You need to add as DNS server in your network settings. If you're using linux, edit /etc/resolv.conf and add a new nameserver line to the top:

Finally, restart Dnsmasq:-

 sudo /etc/init.d/dnsmasq restart

Apache Stuff

Now all you need to do is set up a virtual host:

Restart apache and you're done.

Or! If you're Using Rails

If you're using Rails, you won't need to set up a virtual host in Apache. Just start your server:

 rails s

Then browse to the domain you set up, like so:


Also, on a seperate note... You may notice internet pages are loading faster. This is because you now have a local DNS server cache. Therefore, resolving domains is a lot faster. You get this as a free side effect.