So I have an Ubuntu multi server ISPconfig setup. I followed the instructions for the perfect multilevel server for the Debian server but added the configurations for Ubuntu. I have a Web/Master server, mail, db, ns1 and ns2. The configuration is working great currently. However I needed to add another server that is using nginx for it's webserver as my customer needs to have a server with the BigBlueButton on it. BigBlueButton currently only support nginx so I followed the instructions on installing nginx and such to prepare to add the server to ISPconfig. I have successfully added the server to the ISPconfig master server. And when I create a web domain on the new server, the path and everything is created. However when I try to go to the domain, it goes to the first domain's original index.html file. So my problem is that my main server doesn't forward the domain to the new server. How can I find out what is going on? I have looked at logs and others and I just can't locate it.
Yes. The DNS is setup. I have the resolv.conf file pointing to the DNS servers. How does it work workflow vice? Does it first hit the main panel and then it points it to the next server? Also the DNS servers need to point to the internal IP addresses correct? I only have one External IP address.
Is this a DNS server for internal use only? Then the resolv.conf of the client PC's should point to the DNS server. The resolv.conf of the DNS servers however should point to a real DNS server (like 8.8.8.8 and 8.8.4.4 - Google's nameservers). If this is for internal use only, then yes.
So am I to understand that I need two external IP addresses? One for each web browser? And they can not be behind a firewall? I am trying to understand how things work. I thought that ISPconfig reroutes the web traffic once it comes through the initial firewall.
Two IP addresses for a web browser? I'm sorry, but I don't understand what you're looking for. Maybe you can describe your problem in more detail.
OK. I setup my system in accordance to the multi server setup that you can find in the ISPConfig Manual. As I however was running it on Ubuntu there was some changes that needed to be made. I had the following in a working configuration: Web server running Apache2 that serves as Webserver and ISPconfig Panel Mail server running Dovecot DB server with Mysql NS1 and NS2. These are all behind one Router with firewall. I only have one External IP address so they are all sharing. What I want to do is to add a server that handles a program called the BigBlueButton. It is a video sharing program that is open source and are targeting educational institutions. It works with the CMS TikiWiki. I created a second web server with Ubuntu 10.04 as BigBlueButton. BigBlueButton server uses FreeSwitch and Nginx among other things. I installed Nginx in accordance to the ISPconfig instructions. I connected the server to the main server, and when I create a domain in ISPconfig and points it to the new server, it gets created. However when I try to get to the server, using the domain name I sent over there, instead of trying to hit the new server, it hits the old server and I get the generic Apache index.html file message. I thought that when I hit the ispconfig server, that it would redirect the traffic to the right server behind the firewall. That may just be completely faulty thoughts as I may not understand how the DNS and Firewall works together with the ISPconfig (which is more likely the reason). So my question is this. Do I need to have more External IP addresses, or could I possibly solve the issue by creating my own router where I have more control. For example, could I create an NS server that can also act as DHCP server and router? And add it to the ISPconfig for control? Or would this not be such a good idea? It is a cool thought at least. That would also allow for easy IPv6 addition as we can use the tunneling if needed. (off topic) And Falko. Thanks for helping me out on this one. You are an amazing help and I love the work you do here!
Yes, because you can forward a port to just one IP. So if you have forwarded port 80 to your old server, all traffic on port 80 will go to that server. Another solution would be to use different ports, but then you always have to use that port in the URL.
