virtualhost and dynamic ip

[Guest_imported]

Hi,
im trying to configure apache with virtualhost

the router get everydy new address IP and my server is runnig
on ip 192.168.2.33
my domaine is

http://www.mydomaine.com

how can i configure my server so if someone tape

http://www.mydomaine.com

he will be directed to my server
i did the following

<VirtualHost 192.168.2.34 217.235.1.68>
servername

http://www.mydomaine.com

DocumentRoot /usr/local/httpd/htdocs/mypage
</VirtualHost>

it's not the best way because the address changes.

thanks for help.
eliap

 

[mithrilhall]

Go to

http://www.no-ip.com

and sign up for free. Then download and install their IP updater.

 

[Wullie]

Hi,

Another service is DNS2GO..

http://dns2go.deerfield.com

Wullie

http://www.freshlookdesign.co.uk

http://www.searchit-now.co.uk

http://www.survivorhelp.co.uk

 

[HuggerFanta]

You can also use

http://www.dyndns.org

to get it working, i think!!! --------------------------------------
Kind regards;
HuggerFanta

 

[RhythmAce]

You can use any of the dns pointer services mentioned above. What happens is you sign up with a pointer service and have your domain name assigned to their dns server's ip. Your server will keep their servers updated with the latest ip and when a request comes in for your domain, it gets sent on to your new ip address. You will set your server to listen to ALL ip adddresses on ALL ports (in case 80 is blocked by your isp). As far as virtual hosts go, I'm not sure if that will work with most of the dns pointer services out there without buying extra services which may have a cost assoiciated with it. Good luck.

 

[Wullie]

You will set your server to listen to ALL ip adddresses on ALL ports (in case 80 is blocked by your isp)

There is NO reason to do this. It is totally pointless.

As far as virtual hosts go, I'm not sure if that will work with most of the dns pointer services out there without buying extra services which may have a cost assoiciated with it.

Dns2Go will work with as many as your require, it just forwards all requests to your server.

Hope this helps Wullie

http://www.freshlookdesign.co.uk

http://www.searchit-now.co.uk

http://www.survivorhelp.co.uk

 

[RhythmAce]

Pointless my foot ) If he has a dynamic ip, his ip changes all the time. If he tells httpd to listen for another ip it won't answer to the one he last entered into httpd.conf. Many ISPs also block port 80 so if he tells httpd to only listen on port 80, it ain't gonna hear much. Setting his namebased virtual host to &quot;*&quot; would not be pointless in this case - do I hear an AMEN?

 

[Wullie]

Hi mate,

There is no reason to include your ip in your httpd.conf.

If your isp blocks one port, then set up port forwarding and change the port that apache listens to.. If you only have one port that the domains are pointing to, then why set all ports to listen? The namebased virtualhost * does not tell apache to listen to any port other than you have specified in either the PORT or LISTEN options.

I never said to set apache to listen on port 80.. Use 8080..

Hope this helps Wullie

http://www.freshlookdesign.co.uk

http://www.searchit-now.co.uk

http://www.survivorhelp.co.uk