For Drupal 7 sub-domain installation is sites.php the same as 6's use of symbolic link folder? I have a working Drupal 6 using a shared Drupal install on a shared Linux server. I've just installed D7. I'm not sure if sites.php is set up correctly (see below). And I can't find good information on this sites.php file to be sure I set it up correctly. This Drupal.org page describes the correct installation situation, but sadly does not mention sites.php (>_&lt;) This Drupal forum poster has the same "Server Not Found" error, but shows completely wrong sites.php example--the set up is not clear.

Is sites.php do the same thing that a symbolic link folder did in Drupal 6. Can I ignore this file?

My sites.php file,

 $sites['mondo7'] = 'mondo7.mydomain.com';


and I tried it the other way, 

 $sites['mondo7.mydomain.com'] = 'mondo7';


Both show up "Server Not Found".
sites.php exists so you can fake out the normal multi-site operation, like mapping 'localhost' to 'foo.mysiteroolz.com'. Ideally you wouldn't use it in a production server.

In a live-to-the-internet site, you don't want to have sites.php (unless you specifically know why you do), and you want your subdomain to resolve to the same IP and directory as the domain. Then just have a subdirectory in /sites. So:

drupal/sites/default/ will have settings.php and files for mydomain.com

drupal/sites/mondo7.mydomain.com/ will have settings.php and files for mondo7.mydomain.com.

Then in your dev setup, you'd have a sites.php file that says something like 'localhost' =&gt; 'mondo7.mydomain.com' This tells Drupal which site directory gets the attention when a request comes for localhost.

HTH.