Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Apache httpd.conf

Status
Not open for further replies.

Joe689

Technical User
Oct 1, 2003
6
0
0
US
Would someone possibly try to explain to me how to using the httpd.conf I can get it to update my ip address since it is not static. I have file called zoneclient.dat, that stores my current ip address and submits it to my dns zone. Possibly maybe i can call the virtual host to pull the ip. I am on dsl and my ip can change upto twice aday. I have a copy of my httpd.conf at if someone would even help me with editing it and possibly email it that would be great or any insight into this.

I have dsl and have a dynamic ip. The ip changes at least once day and i dont like reconfiguring it by hand every time it changes. From other posts, it seemed that httpd.conf controlled what ip apache is listening too.
I already have dynamic dns that updates by itself, so the dns isn't a problem. I am running red hat linux. From other posts they suggested using "*", some "127.0.0.1" using at the virtual host name.


Thanks
Joe
 
You could also use _default_:80 in the virtualhost listening and use BindAddress * for the IP binding.

This will then have it answer on any request that hits that apache.

 
You don't have to change the ip in httpd.conf every time your ip changes. By default, apache listens for all addresses on port 80. Unless you bind to a particular ip. In this case it looks like you are binding to the loopback device (127.0.0.1). Your vhost directive should look like this: <VirtualHost *:80> and <VirtualHost *:443>. You don't want an ip anywhere in the following directives either, Listen, Port or Bind. Now there is a dns issue with your dns pointer service. To use name based addressing, your service must provide the header information and not strip it off. Some pointer services do that then apache can't tell which domain is being requested. If this is not the case and they are setup to handle multiple domains for you then you should be set to go. A couple more things: When you use vhosts, the one defined in &quot;Main&quot; never gets served. The first vhost defined becomes the default in case no match is found. The second thing I wanted to point out is that any directive you have in a directory container, applies to all sub-directories below it unless you redefine it.
 
The dhcp stuff should not be resetting ips so often. Sounds like a real problem with network configuration. 30 days on expiration for ip addresses ought to work fine.

Can you have a static ip assigned to you. Have your SA reserve an ip address for you with the DHCP server. Otherwise, if your ip changes all the time, users that bookmark your site will not be able to return, unless they know the new ip anyway.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top