Is there a how-to for the scenario bellow Scenario: I have one server for wich I have purchased one static IP address. After setting up ISPconfig I can sent and received email and view my web page on the website.ca which I aslo set up the dns sever for with the records. My ISP ask me put their DNS server address at the domain registrar. I did this for the ,ca and the .net. I also added ns1.my_static_ip_sddres at the registrar and deleted their domain server. So at the domain registrar there 3 pointers. Two points the my ISP domain and one points to my static address. The ISP as put a pointer in those two web server pointing to my IP address. The result is the .ca works but i can get the .net dns to reply. I need to add the ,com, .org, .biz, etc. I want to create two websites on the .com and the .net. and point the others to the .com. At this point, repeating myself, only the .ca works and the .net does not. What do you suggest. Do I need 4 network adapter connected to my private network each having its own domain names? I have not been able to assign working satic internal addrress to the othe two network cards. I am totally new with Linux/ispconfig and I apologized if any of my questions are simplistics
I'm not sure I totally understand your question. I believe you are asking how to have one server that answers requests for several domains. It appears you have several domains such as "example.com", "example.net", "example.biz", etc. Do you plan to run different websites at each domain? Or do you plan to have one website that is served regardless of which domain (.com, .net, and .bix) is entered by the user? If you want to have different websites for each domain, you would simply setup new sites through ISPConfig treating them all differently. If you want to have one website served to all the domains, you are going to need to use a redirect or have multiple Apache vhost files. There are a few different ways to accomplish this with various advantages and disadvantages. Are you running your own DNS server on your internal network (not your ISP DNS servers)? If not, I would suggest running an internal DNS server which you use to test your DNS records and webserver setup before you deal with publicly available DNS servers. It might take a little more time up front, but the lessons you learn will be invaluable.
I'm not sure I totally understand your question. I believe you are asking how to have one server that answers requests for several domains. It appears you have several domains such as "example.com", "example.net", "example.biz", etc. Do you plan to run different websites at each domain? YES Or do you plan to have one website that is served regardless of which domain (.com, .net, and .bix) is entered by the user? I would like to have to website using the .com for presentation and the .net for networking people If you want to have different websites for each domain, you would simply setup new sites through ISPConfig treating them all differently. I have done that but it does not work. I am testing the .ca and the .net. I have entererd the same info on each domain provider. I have used the instruction for bacic DNS at the ISPconfig web site. The result in entering the NS address of my ISP and my NS domain is a lame server. I need to resolve.this. I desire to be authoritative for all my domains. Right now the .ca works but not the .net. My ISP has put a PTR for to my IP Address for both sites If you want to have one website served to all the domains, you are going to need to use a redirect or have multiple Apache vhost files. There are a few different ways to accomplish this with various advantages and disadvantages. What wold suggest that I read? Are you running your own DNS server on your internal network (not your ISP DNS servers)? If not, I would suggest running an internal DNS server which you use to test your DNS records and webserver setup before you deal with publicly available DNS servers. It might take a little more time up front, but the lessons you learn will be invaluable. I would like to do this for you are right on this. I could do this with windows in a very short time. I do not want to use window server. I am new to Linux but everyone I talk tooo suggested to use it if I did not want the headache of securing windows. I have a lot of experience with windows but none in Linux. I hope that choosing Debian was the right choice. I talk way too much! Can i be authoritative with one static IP address? So far ecerything leads to a big no.
Yes, you can be authoritative with one static IP address. This is actually my current setup. I also use Debian Linux for all my servers. However, the setup you described does not have you being the authoritative DNS source. You mentioned that your DNS server is lame. Who is hosting the DNS records for your domains? I suspect this is a DNS problem. DNS took me a long time to finally grasp and understand along with a lot of trial and error. I find it easiest to take it one step at a time. I would focus on one domain at a time as well. First, I think you need to be using "A" records instead of "PTR" records. An "A" record in DNS translates a domain address to an IP address. To check DNS is working right, I like to use the NSLookup function found at http://www.zoneedit.com/lookup.html. Enter your domain and report back as to whether the IP address returned is the public IP address of your server. Just to confirm, are you using a static public IP address for your server?
I am grateful for your time to reply. My ISP is cogeco cable in Canada. One static IP cost 100 month and if I want to upgrade to more the next step is 200 month. I will not comment on this... The problem started at the domain registrar which ask for too dns address. It will not accept one only. I called cogeco tech support and they said to enter the two DNS server address they gave me on sign up and I should work. One of the address they gave me is not accepted by one of the registrar? Anyway I put the two address given plus my IP address for ns1. I do not want my ISP or any other to be authoritative as it is my money that is being spent and I like assume my own stuff. Again the problem at the registrar is that they want two IP addresses for the DNS. At the moment, I am reading the debian network tutorial (awesome) because I have not been able to set up my three network cards. If I entered for each a static address on the same subnet and mask it acts up. I talk way too much... Thanks again
Ouch. I pay $5 USD a month for one static IP. Each additional is another $5. This is common. For the time being, I would suggest getting your domain working with a third party DNS provider. Once the domain is working, you can move the DNS records to your server once it is no longer lame. I like to use ZoneEdit for this purpose. They used to allow free accounts to have five domains. I think they now allow two free domains. Once you have created an account and entered your domain, they will provide you with two nameserver addresses. You will enter these addressed into the two required fields at the registrar. Please note that during this time, the ZoneEdit servers will be the authoritative DNS source for your domain(s). Again, I would take things one step at a time. Your are taking some pretty big bites. I would get your server up and running with one network interface first. Then you can come back and activate the other interfaces later. I would also suggest this route from a security standpoint. I wouldn't connect your server to both a public and private network until you have a better idea how everything is working together. Otherwise, you could potentially compromise your private network if the configuration is incorrect. Are you planning to assign your public IP address directly to the server? Or is there a firewall or gateway between the server and the Internet?
It is good to have a healthy fear when it comes to security. However, a good three interface firewall would allow you to have your public servers in a DMZ network segment, local network machines in a protect LAN network segment, and a public interface. If I remember correctly, my Linux based firewall has an extremely small footprint. I think it has 4 GB disk and only 128 MB RAM.
This is what a few people have suggested. It is common sense for these providers, i am told, look after security. I realized, reading many post regarding security, that this is an issue for Linux. I had the misconception that Linux was secure. What a nightmare these hackers are and to what end? No, considering that I am getting 5 IPs addresses next week, my home network will not be exposed. Only the .net and the . com will be connected. Thanks, I a in contact with one of my domain registrar and they will point to one IP address. Interesting... I must have done something wrong at the other registrar? I have Cisco business router connected to a Cisco fs726t smart switch. At this moment the server is configured on the DMZ zone of the router. Because I signed up with the large enterprise plan, I will have two server connected directly to the internet. I recall seeing an how-to related to this configuration. One server will become the backup for the other one. The router will be connected to another ip address and will look after my home network. At his point this is what I will do with windows. One domain controller with one backup domain controller. The problem is that I have only a registered 2000 and 2003 version.
I do believe the security "concept" in Linux is more secure. However, the weakest link in the overall configuration is usually the administrator. If the administrator doesn't have a sound networking and/or security understanding, a configuration can be implemented that total bypasses the default security settings. That is why I suggest keeping network physically separated until you have a firm understanding of how all the pieces fit together. I'll admit that I don't have a firm understanding of your overall network setup or what you hope to accomplish with your new servers. At first glance, it seems like you have obtained way more IP addresses than you really would need for your setup. Most of the setups I have worked on assign one public IP address to a gateway router. Often times, that router has firewall responsibilities. Port forwarding is then used to send the appropriate traffic to each internal server. I have worked with a lot of small and medium sized companies hosting all of their services (email, web, ftp, dns, etc.) on one public IP address. If I were dealing with the same prices you mentioned before for static public IP addresses, I would probably reconsider my network design to minimize the number of static public IP addresses required.
Yes 3 too many. We have only teo ISP here with quite a monopoly on what is available. I am waiting for my .net to propagated then I will see if one server setup will work. Atjensen I am appreciative of your time and we will close this link. I am sure your time is not free and going further will have to be private and at the moment I have no money to hire a consultant which will solve all my problem. So I will read and read until I drop dead. But I will get something going as I have at this point. I am reading a book by IAN LLOYD which will be my foundation for web design learning curve. Again thanks. I think the HOW_TO_ that needs to be writen is how to host working multiple dns site on one server using ISP_Config 3.
