I'm still wondering why the webserver address seems to change all the time? Either it should have a static IP or a name which resolves via DNS. Internal PCs should hit the hosts file first, then local DNS, then external DNS to resolve. How many internal hosts (PCs)? You can update a hosts file with a login script and they can be set to search the local net first, before going to the internal DNS server.
So, are you changing the hostname of the server all the time or adding new ones, e.g. webserver1, webserver2, etc., or adding new domains all the time? Considering that any of these involve adding a few lines to a text file for name resolution, I agree with Frank, that this is not hard. Again, it could be even scriptable to add a virtual host to a webserver and update DNS files and restart DNS if this is a frequent occurance.
-----Original Message----- From: Behalf Of Frank Wiles
On Sat, 28 Jan 2006 18:42:56 -0600 hanasaki [email protected] wrote:
harder in the sense...
wouldn't it be much easier to just add a new virtual host to the webserver and be able to hit it w/o having to update internal DNS (ie: only the external world dns).
With something link BIND 9 which can do split DNS views of the outside world and inside world having "split DNS" literally means you have to change two lines of zone configs instead of one.
So for example, if you're adding new-host.domain.com to both you have have to add it into db.domain.com-external and db.domain.com-internal and rndc reload the config. I'm still wondering why this is "hard".
--------------------------------- Frank Wiles [email protected] http://www.wiles.org ---------------------------------
--- "Kelsay, Brian - Kansas City, MO" wrote:
I'm still wondering why the webserver address seems to change all the time? Either it should have a static IP or a name which resolves via DNS. Internal PCs should hit the hosts file first, then local DNS, then external DNS to resolve. How many internal hosts (PCs)? You can update a hosts file with a login script and they can be set to search the local net first, before going to the internal DNS server.
So, are you changing the hostname of the server all the time or adding new ones, e.g. webserver1, webserver2, etc., or adding new domains all the time? Considering that any of these involve adding a few lines to a text file for name resolution, ...
I am also wondering why you are constantly changing the webserver address. I would think you would want to
to use a static IP for such an important server. If you're using DHCP, which is a good idea from a maintainence perspective, then you simply need to make a manual allocation on the DHCP server for the webserver and any other critical servers. Then you wouldn't have to do all this changing all the time. Seems like you are just making work by constanly fiddling with IP issues. Also, like Brian and others have said, by having the webserver in your hosts file or a local DNS, your internal network wouldn't need to route through the firewall. Unless, of course, you want to route through the firewall. Although I don't see a good reason for this other than tracking internal traffic, which could be done other ways. Or maybe you don't trust your own webserver. Now, if you are constantly changing the physical webserver hardware and using DHCP all you need do is update your DHCP server config with the new MAC address and ... bada-bing bada-boom, all your clients now can find your new webserver.
Brian JD
-
Jack -
Kelsay, Brian - Kansas City, MO