It becomes much harder to access a virtually hosted website if the DNS (Domain Name System) does not function properly. Normally in this case, the user could try and fall back to using the IP address to contact the system but the web browser does not know what host name to send when this occurs. Hence, the server is most likely to respond with a default website, often not the anticipated site of the user. It is not that useful for an average web user but may be beneficial to a site administrator while fixing DNS records. Adding the IP address and host name to the client system’s host file is a good thing to do in this case. At this point, accessing the server with the domain name is most likely to work again. The users, however, should be careful as any changes made to the true mapping between IP address and host name will be overridden by the local setting. Another problem with this kind of hosting is the inability to host more than one secure websites running SSL (Secure Sockets Layer). Running IP aliasing or multiple web server programs is a pretty good way to handle this issue. |