From: Joe C. <jo...@sw...> - 2002-09-26 10:06:43
|
There are ways to save yourself time when debugging such problems by use of 'host' (nslookup if you're on an antiquated OS). # host mycoolnewsub.domain.com nameserver.address.here Where nameserver.address.here is the address of the nameserver where you have added this new subdomain. It will take time for it to trickle down to the worlds nameservers from there. Then, of course, to test your virtual host, you can add the address and subdomain to your /etc/hosts file (assuming a Unix-like OS on your workstation--Windows uses lmhosts or something like that for similar purpose). Then your browser will know how to find your new subdomain even before your local nameservers do, and will contact it in the same manner. If you just enter the IP in the URL space, the default site will be loaded rather than your preferred virtual. Ashley wrote: > Well it works now :) I tried it this morning and it works, just took a > little time to work itself around dns servers I guess. > > Thanks anyway > > Ashley > > -----Original Message----- > Yes, you need to edit the httpd.conf file, create a new v-host just like > you would with an actual domain. Then make sure your DNS has this > subdomain pointing to the correct IP, and bang, your done. -- Joe Cooper <jo...@sw...> Web caching appliances and support. http://www.swelltech.com |