Free web hosting

[alibalavi]

To have free personal web hosting follow this steps

Just download Wampserver from wampserver.com and install it on your computer then fallow this steps:

Configuring Apache to Work over your Network

Try to find the IP address of the computer that the web server is installed on. On Windows type ipconfig in a command box. You should then be able to look at the site from another computer in the same network by typing http://xxx.xxx.xxx.xxx/sites where the x represents your IP address.

For example, on my computer (Windows XP) I type in:
ipconfig

I get:
Quote

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.1.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1

I can then access the web server by typing:
http://192.168.1.10/sites


Proper use of .htaccess and .htpasswd

You can put your .htaccess file anywhere in your website directories. You can also put your .htpasswd file anywhere in or out of your website directories. However, for security reasons, always store your .htpasswd files outside of your website Document Root. Leaving your .htpasswd file in your website directory makes it accessible to the whole world, and they could easily add their own login info and get access to your website. The safest way of doing things it to create directory outside your Document Root for your .htpasswd files. I call my password directory ‘pwds’. So, to make sure the password directory is outside my webroot, on my computer it would look like this:

C:\wamp\pwds

To password protect a directory, create a file called .htaccess and put in the directory you which to protect. Add these lines to your .htaccess file:

AuthUserFile c:/wamp/pwds/.htpasswd
AuthName "Members Only"
AuthType Basic
<Limit GET POST>
require valid-user
</Limit>

Now, you need to save your passwords in your .htpasswd file in encrypted format. You cannot just use someuser:somepass since the password is not encrypted. To get a proper encrypted password, check out this website:
http://www.flash.net/cgi-bin/pw.pl.

Put your user name and password in the boxes, and it will return your user name and your encrypted password. Then copy it and put it in your .htpasswd file in this format:

username:encryptedpassword

save the file and place the .htpasswd file in your C:\wamp\pwds directory and you are ready to use password protected directories.

To learn more about .htaccess and .htpasswd, check out this site:
http://www.htaccesstools.com


Handling PHP “Called to Undefined Function” Errors

If you get any called to undefined function errors while developing your PHP scripts, this is because you need to enable the extension for that function you are trying to use to work. For example, if you are trying to use GD and you are getting the called to undefined function error, it is because you have support disabled for the GD extension in your php.ini file.



So, in our example, to enable support for GD, you will need to enable php_gd2 in the php.ini file. WAMP includes a menu to do this for you so you don’t have to worry about editing a config file yourself. So, to enable an extension for GD, use the WAMP tray icon menu and right click on the icon:

Go to: PHP Settings -> PHP Extensions -> php_gd2

After you enable the new extension, WAMP will automatically restart Apache for the new setting to take effect.


MySQL “Client does not support authentication protocol requested by server” Errors

MySQL 5.0 uses an authentication protocol based on a password hashing algorithm that is incompatible with that used by older (pre-4.1) clients. If you upgrade the server from 4.0, attempts to connect to it with an older client may fail with the following message, “Client does not support authentication protocol requested by server; consider upgrading MySQL client”.
MySQL Website Documentation

To get this to work, you will need to update your MySQL privileges to work with the new format. To do this you will need to open the MySQL Console. Left click on the WAMP tray icon, and select:

MySQL -> MySQL Console

The console will now start and ask for a password. If you have not changed the default root user’s password, then just press enter since the root user does not come with a password set. If you did add a password for the root user, then you will need to enter that new password in the password field. Then press enter and you will see the MySQL prompt.

Enter this command statement. You will need to change some_user below to the user you wish to change. If you need to change the root user, then change it to root, if you need to change some other user, then set it to that user. Then you will need to enter a new password for this user in the newpsw part

SET PASSWORD FOR -> 'some_user'@’localhost' = OLD_PASSWORD('newpwd');

When you are finished running the command, press Cont + Q to leave the MySQL console. Now restart MySQL for the new settings to take effect.



Tips and Tricks

Apache: Using WAMP as a production server and only allowing your certain people to have access your server.

You can use Apache’s Allow and Deny directive to allow or deny certain hosts, domains, ip address, and other types.

For example, to use your WAMP server as a production server, but only allow your friends to have access to your server, put your server into Offline Mode, and then open up your Apache config file httpd.conf ([ i]WAMP Trey Icon -> Config Files -> httpd.conf[/i] ) and find:

Order Deny,Allow
Deny from all
Allow from 127.0.0.1

For each friend you want to allow, add their IP address to the allow list. If your friends do not know their IP address, tell them to surf to WhatIsMyIP.com (this is not a website owned by me).

After you are finished added allowed IPs, save the file and restart Apache for the new settings to take effect.

Also note that there are many different ways to Allow and Deny people. To see more on how to do that, check out Apache’s website.

For more info on Allow

For more info on Deny

For more info on Order


Setting up Apache to use a Domain Name

Here is a tutorial on how to setup Apache 2.x to host a domain name with Virtual Host using Dynamic DNS. In order to do this, you will need a domain name. If you don’t have one, you can register on at http://www.godaddy.

A quick note: I will be using domainname1.com and domainname2.com in the examples here. Remember to change these example domain names with your actual domain name(s).

The first step you need to do is signup for an account at http://www.zoneedit.com. ZoneEdit is one of the most popular Dynamic DNS services out there, and they are also free. Another great feature about the site is it is loaded with tutorials and examples on how to setup and manage DNS and other settings for your domain name.

Before we go any further, there are some technical terms you need to know:

For more info on NameServer, check out:
[en.wikipedia.org]

For more info on Dynamic DNS check out:
[en.wikipedia.org]

More info on all DNS Record types:
[en.wikipedia.org]

Now that you have signed up for an account at ZoneEdit, login to your account. Click on the Add Zones link at the top of the page. In the box to the right of Enter Domain Name enter your domain name. Enter it in the format domainname.com. Do not add http:// or www. in front of your domain, just enter the domain name. Click on the Add Zone button just below the text box you entered your domain name in to add your domain.

After you press the Add Zone button, you will be taken to a page with this message at the top:

IMPORTANT: Before your "domainname1.com" site is live you must contact your registrar (the people from whom you purchased this domain name) and tell them to change its nameservers to:

This message tells you what NameServer’s to use for your domain name. Just below that warning will be two NameServer addresses in this format (don’t worry if your NameServer’s do not match mine in this example, ZoneEdit uses many different NameServer’s, all with different addresses).
Nameserver 1: ns2.zoneedit.com (69.72.158.226)
Nameserver 2: ns7.zoneedit.com (216.122.7.155)

So, the two NameServer’s I need to use for my domain name are:
ns2.zoneedit.com
ns7.zoneedit.com

Now, your NameServer’s might be different than mine here. You should write your NameServer’s down now because you are going to need them later.
Now click on the Start Editing Zone button at the bottom of the page. You now need to do what in technical terms is called creating an A record to tie your IP address to your domain name. So, now click on the IP Addresses link. You will now be taken to the IP Addresses page.

Here is where we will create two A records. One will tie domainname1.com to your IP address and the other will tie http://www.domainname1.com to your IP address. This way people can access your website if the type domainname1.com and http://www.domainname1.com. To create the first record, leave the box below Name blank. In the box under Numeric IP, enter your IP address. If you do not know your IP address, go to http://www.whatismyipaddress.com. Now click on the Add New IP Address button. You will now be prompted with this confirmation:

Are you sure you would like to add the following IP Addresses?
Both "domainname1.com" and "www.domainname1.com" will have the IP 71.152.144.215.

Click on the first Yes button at the top and it will to add both domainname1.com and http://www.domainname1.com. After you click the Yes button you will be taken back to the IP Addresses page and you will now see both domainname1.com and http://www.domainname1.com listed there with your IP address next to them.

You are now done dealing with ZoneEdit. Now you will need to login to wherever you registered your domain name and change the NameServer settings for that domain. I use GoDaddy.com as my domain name register, and since they are the most popular domain name register on the net, I will use them in this demo. If you do not not use GoDaddy, you can still change the NameServer settings yourself. If you cannot figure out how to do it, contact your domain name registers tech support and ask them to set your domain name’s NameServer’s to the NameServer’s ZoneEdit gave you.

Log in to your GoDaddy account. Then click on the My Account link. Now scroll down to about the middle of the page, and click on the Manage Domains link. Now you are at your domain name administration screen. Now click on the domain name you want to use (it needs to be the same one you setup at ZoneEdit).

If your domain name is locked, you will need to unlock it before you can change the NameServer setting. Click on the Lock button in the top menu and you will be taken to the lock page. Select Unlock and press the OK button. One the next screen just click on the OK button. Now click on the NameServers button in the top menu to set the NameServer’s. You may get a message saying “An update is being processed for the selected domain. You will be able to change nameservers when this processing is done. Please try again later.” If you get that message it just means your domain name lock request is still being processed by GoDaddy. It may take a few minutes (I have waited up to 10 minutes once) for the processing to finish. Once it has finished processing you will be able to change the NameServer settings.

So, if are not at the Set Nameservers page, click the Nameservers button in the menu at the top of the page. In the Nameserver 1 box, enter the first NameServer address from ZoneEdit. In the box next to Nameserver 2, enter the second NameServer from ZoneEdit. Now click on the OK button to submit your new NameServer’s to GoDaddy. Now click the OK button on the next screen.

That is it. You have now successfully changed your NameServer settings for your domain name now. If you have any other domains you want to use, now do the same process for those domains. Now you need to lock your domain name. Use the same procedure I wrote about above.

Now you will need to create a location on your server where you are going to store all your virtual hosted websites. To make things easier, I suggest you put all your virtual host websites in one location, versus all over your computer. This will make using, and editing your website files much easier, since you now they are in one place versus all over your computer. I put all mine in a folder I call users in my wamp folder. That would be:
C:\wamp\users

Now create a folder inside your users folder and name it your domain name. So, in this example, I will name it dominname1.com. That would be:
C:\wamp\users\dominname1.com

Now you need to create two new folders in the domainname1.com folder, one name logs and one named public_html. The logs folder is where your apache error and access logs for that domain name be stored. The public_html folder will store all your domain name’s website files (html, php, css, images, etc). That would be:
C:\users\dominname1.com\logs
C:\users\dominname1.com\public_html

Now we will need to edit your Apache Virtual Host configuration file. Open up the file httpd-vhosts.conf, located:
C:\wamp\Apache2/conf/extra/httpd-vhosts.conf.

Find this line:
NameVirtualHost *:80

If that line has any pound sign ( # ) in front of it, remove it to enable VirtualHost.

On the next line add this:
<VirtualHost *:80>
ServerAdmin admin@domainname1.com
DocumentRoot C:/wamp/users/dominname1.com/public_html
ServerName http://www.domainname1.com
ServerAlias domainname1.com
ErrorLog C:/wamp/users/dominname1.com/logs/error.log
CustomLog C:/wamp/users/dominname1.com/logs/access.log common
</VirtualHost>

If you have any more domain names you want to add, add them just below the previous example above. Here is an example:
<VirtualHost *:80>
ServerAdmin admin@domainname1.com
DocumentRoot C:/wamp/users/dominname1.com/public_html
ServerName http://www.domainname1.com
ServerAlias domainname1.com
ErrorLog C:/wamp/users/dominname1.com/logs/error.log
CustomLog C:/wamp/users/dominname1.com/logs/access.log common
</VirtualHost>
<VirtualHost *:80>
ServerAdmin admin@domainname2.com
DocumentRoot C:/wamp/users/dominname2.com/public_html
ServerName http://www.domainname2.com
ServerAlias domainname2.com
ErrorLog C:/wamp/users/dominname2.com/logs/error.log
CustomLog C:/wamp/users/dominname2.com/logs/access.log common
</VirtualHost>

Now you need to save the file httpd-vhosts.conf and restart Apache for the new settings to take effect. Note however, that it will take between 12-48 hours for your NameServer changes for your domain name to take effect. This means it will not work until it has fully propagated through the DNS system.

More info on domain name propagation:
[en.wikipedia.org]

you now need to edit a line in the httpd.conf file to allow virtual host. open c:\wamp\apache2\conf\httpd.conf and find this line:
#Include conf/extra/httpd-vhosts.conf

remove the pound sign ( # ) at the beginning of that line to enable this setting. save the file and restart apache for the new setting to take effect.

I have noticed with GoDaddy, domain name propagation only takes a few minutes. To see if your domain name has fully propagated, use dnstools.com. Enter your domain name in the box. If your see your ZoneEdit NameServer’s listed in the whois report, your domain name has fully propagated. If not, you will need to wait a bit longer and try again.

[francksenior]

very interesting and complete article, congratulation and thank you

[standingoten]

Hosting this way (building and hosting yourself) is highly complex and in the long run isn't worth it. You run the risk of your ISP closing you down for violating their terms of service as well.

[huggs]

This is very interesting way to get free hosting.There were hundreds of sites that offers free hosting.Generally they either cost you in time, web hosting restrictions, or modifying your free web pages by adding popups, banners, or other adverts. When looking for free web hosting (especially on search engines), you should beware that there are also a large number of commercial web hosts that claim to offer free hosting services, but those often have a catch, such as paying an excessive amount for a domain name or other service, and therefore aren't really free. The free free hosting guide below will give you some tips for finding the right free webhosting comapny for you.

__________________________

[iFuturz]

(04-15-2012 12:52 AM)alibalavi Wrote:  To have free personal web hosting follow this steps

Just download Wampserver from wampserver.com and install it on your computer then fallow this steps:

Configuring Apache to Work over your Network

Try to find the IP address of the computer that the web server is installed on. On Windows type ipconfig in a command box. You should then be able to look at the site from another computer in the same network by typing http://xxx.xxx.xxx.xxx/sites where the x represents your IP address.

For example, on my computer (Windows XP) I type in:
ipconfig

I get:
Quote

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.1.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1

I can then access the web server by typing:
http://192.168.1.10/sites


Proper use of .htaccess and .htpasswd

You can put your .htaccess file anywhere in your website directories. You can also put your .htpasswd file anywhere in or out of your website directories. However, for security reasons, always store your .htpasswd files outside of your website Document Root. Leaving your .htpasswd file in your website directory makes it accessible to the whole world, and they could easily add their own login info and get access to your website. The safest way of doing things it to create directory outside your Document Root for your .htpasswd files. I call my password directory ‘pwds’. So, to make sure the password directory is outside my webroot, on my computer it would look like this:

C:\wamp\pwds

To password protect a directory, create a file called .htaccess and put in the directory you which to protect. Add these lines to your .htaccess file:

AuthUserFile c:/wamp/pwds/.htpasswd
AuthName "Members Only"
AuthType Basic
<Limit GET POST>
require valid-user
</Limit>

Now, you need to save your passwords in your .htpasswd file in encrypted format. You cannot just use someuser:somepass since the password is not encrypted. To get a proper encrypted password, check out this website:
http://www.flash.net/cgi-bin/pw.pl.

Put your user name and password in the boxes, and it will return your user name and your encrypted password. Then copy it and put it in your .htpasswd file in this format:

username:encryptedpassword

save the file and place the .htpasswd file in your C:\wamp\pwds directory and you are ready to use password protected directories.

To learn more about .htaccess and .htpasswd, check out this site:
http://www.htaccesstools.com


Handling PHP “Called to Undefined Function” Errors

If you get any called to undefined function errors while developing your PHP scripts, this is because you need to enable the extension for that function you are trying to use to work. For example, if you are trying to use GD and you are getting the called to undefined function error, it is because you have support disabled for the GD extension in your php.ini file.



So, in our example, to enable support for GD, you will need to enable php_gd2 in the php.ini file. WAMP includes a menu to do this for you so you don’t have to worry about editing a config file yourself. So, to enable an extension for GD, use the WAMP tray icon menu and right click on the icon:

Go to: PHP Settings -> PHP Extensions -> php_gd2

After you enable the new extension, WAMP will automatically restart Apache for the new setting to take effect.


MySQL “Client does not support authentication protocol requested by server” Errors

MySQL 5.0 uses an authentication protocol based on a password hashing algorithm that is incompatible with that used by older (pre-4.1) clients. If you upgrade the server from 4.0, attempts to connect to it with an older client may fail with the following message, “Client does not support authentication protocol requested by server; consider upgrading MySQL client”.
MySQL Website Documentation

To get this to work, you will need to update your MySQL privileges to work with the new format. To do this you will need to open the MySQL Console. Left click on the WAMP tray icon, and select:

MySQL -> MySQL Console

The console will now start and ask for a password. If you have not changed the default root user’s password, then just press enter since the root user does not come with a password set. If you did add a password for the root user, then you will need to enter that new password in the password field. Then press enter and you will see the MySQL prompt.

Enter this command statement. You will need to change some_user below to the user you wish to change. If you need to change the root user, then change it to root, if you need to change some other user, then set it to that user. Then you will need to enter a new password for this user in the newpsw part

SET PASSWORD FOR -> 'some_user'@’localhost' = OLD_PASSWORD('newpwd');

When you are finished running the command, press Cont + Q to leave the MySQL console. Now restart MySQL for the new settings to take effect.



Tips and Tricks

Apache: Using WAMP as a production server and only allowing your certain people to have access your server.

You can use Apache’s Allow and Deny directive to allow or deny certain hosts, domains, ip address, and other types.

For example, to use your WAMP server as a production server, but only allow your friends to have access to your server, put your server into Offline Mode, and then open up your Apache config file httpd.conf ([ i]WAMP Trey Icon -> Config Files -> httpd.conf[/i] ) and find:

Order Deny,Allow
Deny from all
Allow from 127.0.0.1

For each friend you want to allow, add their IP address to the allow list. If your friends do not know their IP address, tell them to surf to WhatIsMyIP.com (this is not a website owned by me).

After you are finished added allowed IPs, save the file and restart Apache for the new settings to take effect.

Also note that there are many different ways to Allow and Deny people. To see more on how to do that, check out Apache’s website.

For more info on Allow

For more info on Deny

For more info on Order


Setting up Apache to use a Domain Name

Here is a tutorial on how to setup Apache 2.x to host a domain name with Virtual Host using Dynamic DNS. In order to do this, you will need a domain name. If you don’t have one, you can register on at http://www.godaddy.

A quick note: I will be using domainname1.com and domainname2.com in the examples here. Remember to change these example domain names with your actual domain name(s).

The first step you need to do is signup for an account at http://www.zoneedit.com. ZoneEdit is one of the most popular Dynamic DNS services out there, and they are also free. Another great feature about the site is it is loaded with tutorials and examples on how to setup and manage DNS and other settings for your domain name.

Before we go any further, there are some technical terms you need to know:

For more info on NameServer, check out:
[en.wikipedia.org]

For more info on Dynamic DNS check out:
[en.wikipedia.org]

More info on all DNS Record types:
[en.wikipedia.org]

Now that you have signed up for an account at ZoneEdit, login to your account. Click on the Add Zones link at the top of the page. In the box to the right of Enter Domain Name enter your domain name. Enter it in the format domainname.com. Do not add http:// or www. in front of your domain, just enter the domain name. Click on the Add Zone button just below the text box you entered your domain name in to add your domain.

After you press the Add Zone button, you will be taken to a page with this message at the top:

IMPORTANT: Before your "domainname1.com" site is live you must contact your registrar (the people from whom you purchased this domain name) and tell them to change its nameservers to:

This message tells you what NameServer’s to use for your domain name. Just below that warning will be two NameServer addresses in this format (don’t worry if your NameServer’s do not match mine in this example, ZoneEdit uses many different NameServer’s, all with different addresses).
Nameserver 1: ns2.zoneedit.com (69.72.158.226)
Nameserver 2: ns7.zoneedit.com (216.122.7.155)

So, the two NameServer’s I need to use for my domain name are:
ns2.zoneedit.com
ns7.zoneedit.com

Now, your NameServer’s might be different than mine here. You should write your NameServer’s down now because you are going to need them later.
Now click on the Start Editing Zone button at the bottom of the page. You now need to do what in technical terms is called creating an A record to tie your IP address to your domain name. So, now click on the IP Addresses link. You will now be taken to the IP Addresses page.

Here is where we will create two A records. One will tie domainname1.com to your IP address and the other will tie http://www.domainname1.com to your IP address. This way people can access your website if the type domainname1.com and http://www.domainname1.com. To create the first record, leave the box below Name blank. In the box under Numeric IP, enter your IP address. If you do not know your IP address, go to http://www.whatismyipaddress.com. Now click on the Add New IP Address button. You will now be prompted with this confirmation:

Are you sure you would like to add the following IP Addresses?
Both "domainname1.com" and "www.domainname1.com" will have the IP 71.152.144.215.

Click on the first Yes button at the top and it will to add both domainname1.com and http://www.domainname1.com. After you click the Yes button you will be taken back to the IP Addresses page and you will now see both domainname1.com and http://www.domainname1.com listed there with your IP address next to them.

You are now done dealing with ZoneEdit. Now you will need to login to wherever you registered your domain name and change the NameServer settings for that domain. I use GoDaddy.com as my domain name register, and since they are the most popular domain name register on the net, I will use them in this demo. If you do not not use GoDaddy, you can still change the NameServer settings yourself. If you cannot figure out how to do it, contact your domain name registers tech support and ask them to set your domain name’s NameServer’s to the NameServer’s ZoneEdit gave you.

Log in to your GoDaddy account. Then click on the My Account link. Now scroll down to about the middle of the page, and click on the Manage Domains link. Now you are at your domain name administration screen. Now click on the domain name you want to use (it needs to be the same one you setup at ZoneEdit).

If your domain name is locked, you will need to unlock it before you can change the NameServer setting. Click on the Lock button in the top menu and you will be taken to the lock page. Select Unlock and press the OK button. One the next screen just click on the OK button. Now click on the NameServers button in the top menu to set the NameServer’s. You may get a message saying “An update is being processed for the selected domain. You will be able to change nameservers when this processing is done. Please try again later.” If you get that message it just means your domain name lock request is still being processed by GoDaddy. It may take a few minutes (I have waited up to 10 minutes once) for the processing to finish. Once it has finished processing you will be able to change the NameServer settings.

So, if are not at the Set Nameservers page, click the Nameservers button in the menu at the top of the page. In the Nameserver 1 box, enter the first NameServer address from ZoneEdit. In the box next to Nameserver 2, enter the second NameServer from ZoneEdit. Now click on the OK button to submit your new NameServer’s to GoDaddy. Now click the OK button on the next screen.

That is it. You have now successfully changed your NameServer settings for your domain name now. If you have any other domains you want to use, now do the same process for those domains. Now you need to lock your domain name. Use the same procedure I wrote about above.

Now you will need to create a location on your server where you are going to store all your virtual hosted websites. To make things easier, I suggest you put all your virtual host websites in one location, versus all over your computer. This will make using, and editing your website files much easier, since you now they are in one place versus all over your computer. I put all mine in a folder I call users in my wamp folder. That would be:
C:\wamp\users

Now create a folder inside your users folder and name it your domain name. So, in this example, I will name it dominname1.com. That would be:
C:\wamp\users\dominname1.com

Now you need to create two new folders in the domainname1.com folder, one name logs and one named public_html. The logs folder is where your apache error and access logs for that domain name be stored. The public_html folder will store all your domain name’s website files (html, php, css, images, etc). That would be:
C:\users\dominname1.com\logs
C:\users\dominname1.com\public_html

Now we will need to edit your Apache Virtual Host configuration file. Open up the file httpd-vhosts.conf, located:
C:\wamp\Apache2/conf/extra/httpd-vhosts.conf.

Find this line:
NameVirtualHost *:80

If that line has any pound sign ( # ) in front of it, remove it to enable VirtualHost.

On the next line add this:
<VirtualHost *:80>
ServerAdmin admin@domainname1.com
DocumentRoot C:/wamp/users/dominname1.com/public_html
ServerName http://www.domainname1.com
ServerAlias domainname1.com
ErrorLog C:/wamp/users/dominname1.com/logs/error.log
CustomLog C:/wamp/users/dominname1.com/logs/access.log common
</VirtualHost>

If you have any more domain names you want to add, add them just below the previous example above. Here is an example:
<VirtualHost *:80>
ServerAdmin admin@domainname1.com
DocumentRoot C:/wamp/users/dominname1.com/public_html
ServerName http://www.domainname1.com
ServerAlias domainname1.com
ErrorLog C:/wamp/users/dominname1.com/logs/error.log
CustomLog C:/wamp/users/dominname1.com/logs/access.log common
</VirtualHost>
<VirtualHost *:80>
ServerAdmin admin@domainname2.com
DocumentRoot C:/wamp/users/dominname2.com/public_html
ServerName http://www.domainname2.com
ServerAlias domainname2.com
ErrorLog C:/wamp/users/dominname2.com/logs/error.log
CustomLog C:/wamp/users/dominname2.com/logs/access.log common
</VirtualHost>

Now you need to save the file httpd-vhosts.conf and restart Apache for the new settings to take effect. Note however, that it will take between 12-48 hours for your NameServer changes for your domain name to take effect. This means it will not work until it has fully propagated through the DNS system.

More info on domain name propagation:
[en.wikipedia.org]

you now need to edit a line in the httpd.conf file to allow virtual host. open c:\wamp\apache2\conf\httpd.conf and find this line:
#Include conf/extra/httpd-vhosts.conf

remove the pound sign ( # ) at the beginning of that line to enable this setting. save the file and restart apache for the new setting to take effect.

I have noticed with GoDaddy, domain name propagation only takes a few minutes. To see if your domain name has fully propagated, use dnstools.com. Enter your domain name in the box. If your see your ZoneEdit NameServer’s listed in the whois report, your domain name has fully propagated. If not, you will need to wait a bit longer and try again.

This was a really awesome read.Very useful information. Thank you


Web Design Solution | Do not post more than 1 link in your signature

[Webcs-Peter]

I don't believe in free hosting.

[standingoten]

(05-14-2012 03:33 AM)Webcs-Peter Wrote:  I don't believe in free hosting.

In this case it isn't free hosting either. You are technically paying for your internet service which provides the bandwidth. This is just self hosting which is counterproductive in today's market.

[Jones82]

That's very quality article! Thanks alibalavi for all the hosting info.

[cheochi]

Fantastic Sharing...Thanks for Info.

[sowmya]

Hi,
If you are in the search for the best web hosting services, then just make a visit to our website. We provide the best hosting service in India be it in terms of the pricing or the customer support that we provide.