I was wondering what are the advantages or disadvantages of use more than one IP address on a web server? I have a server with one IP# that is running Bind for our Name Server, Apache and using name based virtual domains. My Host Provider has given me 4 other IP#'s and I wonder if there are any advantages/ disadvantages to using one IP# for Bind, and another IP# for Virtual domains?

You can use the first two for your nameservers. You can use the first nameserver for name-based hosting accounts. As for the other four, you can use them for sites that need SSL or anonymous FTP.

Using One IP# for Bind
One for Apache Virtual Hosts
One for SSL And
One for FTP
Sounds good, But what are the advantages over just using one IP#

Less CPU usage? Faster SSL connection?

That pretty much sums up the need for ip based sites over name based. :)

SSL and anon FTP need to be ip based or they will be able to be accessed by all the name based sites there will be no seperation.

I tend to use at least two IPs for a box. The first IP is just for my control and configuration access. The second, and/or etc. IPs are for the other servers running in the box.

This allows me to set the firewall rules to be very tight on the first IP, i.e., only allow access to certain ports from the specific IPs I use for admin purposes.

Thats a great Idea to put the Administration stuff on one IP# and lock the IP# down with a firewall while having the Virtual sites on another IP#
I wonder if Bind (named) works better under its own IP#?
or does it matter?

I split my name based accounts into different IPs. I put like 10-20 accounts on each IP. The advantage is if something ever happens to one httpd, the other accounts with other httpds are still working. In turn it also reduces customer inquiries, as less clients have problems.

I also use one IP exclusively for control panel, so control panel can be served at standard ports. It also reduces privacy problem, a portscan to your client's IP will not reveal the control panel port number.