Hosting Questions

I have two domains purchased from GoDaddy, and would like to host my website via LAMP from my residence. Right now I have Frontier FiOS internet, 30mb / 10mb with static IP and a dedicated computer landed on my home network with IP statically assigned by Frontier Router (192.168.1.200). The machine is based on AMD A6 APU running at 3.2ghz on dual cores, has 8gb of DDR3 memory and 3TB of hard disk space in RAID 5 format. I have the ability to load OpenSuSE 13.2 or Ubuntu Server 15.04 to start with, need to have email and MySQL running to assist with hosting my personal site and our family site (two domains) accessible to the outside world. In reading both online ISPConfig manual and help files, it would appear that I need to set up DNS with two nameservers, both pointing to a dedicated web server machine but I only have the one machine and one static IP assigned to my location. GoDaddy has been helpful with getting me started but they are not willing to assist with anything on my side of the connection, understandably so. My questions that I need help with are as follow:

1. Which would be the better server OS between OpenSuSE and Ubuntu?
2. Do I need two static IP addresses and three computers to use ISPConfig 3 for DNS / Web hosting?
3. Can I use the GoDaddy DNS servers and still use ISPConfig to handle the local files, email and website?
4. Is using ISPConfig overkill for my purposes, and if so what are the alternatives?

Thanks in advance.
Sgt. Rock

 

Hello Sgt. Rock,

First of all I have to say it isn't the best thing to host websites, mail and DNS from your own residence. Especially not when you got a kind of network that isn't made to host things like this. If it is for your own use, there shouldn't be a problem with it. However if you want to host services for other people in a professional way I suggest you rent a server from a company.

On the first question I don't know the answer. You can read the differences between those linux distributions online, I have always used Ubuntu or Debian.
2. You do not need 2 servers to host all the services you need. You can host all of them on one server, however this isn't a "smart" option. The internet requires that you need two different nameservers for a better redundancy. You can use one IP and one dedicated server to host 2 different "nameservers", however it will be the same nameserver on the same subnet. Read this small piece of text:

Code:

Secondary servers must be placed at both topologically and
geographically dispersed locations on the Internet, to minimise the
likelihood of a single failure disabling all of them.

That is, secondary servers should be at geographically distant
locations, so it is unlikely that events like power loss, etc, will
disrupt all of them simultaneously.  They should also be connected to
the net via quite diverse paths.  This means that the failure of any
one link, or of routing within some segment of the network (such as a
service provider) will not make all of the servers unreachable. 

4. I don't think it will be overkill since you can manage all your services in an easy way, online on one place. Really usefull to use ISPconfig in my opinion.
I see till answered the rest

 

Thanks to all for the advice. I am leaning toward Ubuntu server as primary OS - the Perfect Server link looks informational and quite useful and I plan to follow the Ubuntu 15.04 layout. My connections are static and the machine is stable using Linux, I am on a stable power grid which vary rarely suffers outages in the most severe of storms during impassable winter days. I am confident that my setup should work for a simple website or two provided I can get ISPConfig 3 setup and running correctly.

My proposal for DNS setup:
ns1.mydomain.com
ns2.mydomain.com
Server Name: WebServer1.mydomain.com
WebServer1 (LAN) address 192.168.1.200 static from Router
WAN address: 50.45.235.XXX per static assignment from Frontier FiOS

Alternate Proposal:
GoDaddy DNS Servers:
NS19.DOMAINCONTROL.COM
NS20.DOMAINCONTROL.COM
Server name: WebServer1.mydomain.com
WebServer1 (LAN) address 192.168.1.200 static from Router
WAN address 50.45.235.XXX per static assignment from Frontier FiOS.

I am assuming that if I create nameservers as listed within my main proposal using ISPConfig 3 and the DNS wizard it should work correctly. Once created, I will register them with my GoDaddy account, and I should open ports 443, 80, 8080 and 53 to the server via my FiOS router. If this works out as I understand it now, I should be able to view my website. If the alternate proposal would be the better path for my intended use please let me know.

Thanks in advance.

 

Yes if I see the information you give us, it shouldn't be a problem to run 1-5 websites on your network.
The first setup should work, if you got any problems let us know.
You probably also need to open port 22,21 for SSH-FTP if you want access from outside and the mailserver ports.

 

OK... I have Ubuntu Server 15.04 up and running, ISPConfig loaded with latest version attached to port 8080. I have set up my client (me) and my site. I am at the point of setting up DNS servers. The plan is to use ns1.(mysite).com and ns2.(mysite).com following the "KISS" principle ...

At this point I am in new territory, is there a sample or walk thru available on correct settings? Would like to get this right the first time thru so I can be on track with my other (family) website when it gets ready.

Thanks in advance!

 

Good to hear you got it running. Well there is alot of information on the internet and I think you can get it working pretty fast. There is a small documentation with some links to tutorials here:
http://docs.ispconfig.org/dns-basics/
The first link could be pretty usefull
Do you want to use your own nameservers or the one from your provider?

 

[QUOTE="Do you want to use your own nameservers or the one from your provider?[/QUOTE]

That is the question.... I am unsure as to which would be more beneficial at this point. If I create ns1 and ns2 successfully as outlined, will it work for outsiders (public) to see my site when they google it or would GoDaddy be better for that purpose.

 

Well the first thing like I said is redundancy. If you got BIND installed and configured like in one of the tutorials it is possible to use your own dedicated server as nameservers. However that would mean that ns1.domain.com and ns2.domain.com will both point to the same IP=> same C-class subnet. That would mean that if one of your items goes offline / doesn't work anymore (network, the configuration for the nameservers etc.) you won't be reachable anymore.

This doesn't mean it is a big issue since you are only using one dedicated server for all your services instead of separated. Then the time to resolve the domain name, this could also be a bit longer on your own nameservers when you compare it with the nameservers of your provider. Anyway I don't think they all are a big issue, since you only want to use the setup for a few personal websites.

 

OK Took the plunge and followed the setup guide for both DNS and Site... When I attempt to access the site - I get site not found errors.

My LAN is using DHCP information on a 192.168.1.xxx network with the router serving up IP addresses to all machines except WebServer and FileServer (both linux boxes). For example my gaming rig is 192.168.1.13 on domain HedHouse.net (internal only) with FQDN as gamer.hedhouse.net when checked with IPCONFIG (windows 7 box). WebServer1 was statically assigned to 192.168.1.200 with domain Handyman-it.com (my purchased domain site) with DNS servers using Handyman-IT.com for domain as well so the FQDN is webserver1.handyman-it.com and the name servers are ns1.handyman-it.com and ns2.handyman-it.com respectively. the WebServer has all neccessary ports forwarded in the router for hosting, FTP and IPConfig.

Should the server and DNS servers be using the LAN domain rather than the website domain?

Thanks.

(Edited for content corrections)

 

Have you got a glue record setup at your domain provider? (looks like you haven't)
Do you have the nameservers redirected with an A record to your IP?

 

There is no option listed for record management at GoDaddy - I have the name servers registered to my location at the moment. Also - there is no onsite A record at GoDaddy either. I may have to contact them for more support if that is needed.

 

You need to make a glue record so the public knows how to find the server that would stand for your nameservers. You can find information online how to add a glue record in godaddy like this:
https://www.zerigo.com/docs/managed-dns/glue_records_at_godaddy
I haven't used godaddy before so I don't know how their control panel looks like.

Indeed, when you change the nameservers of your domain Handyman-IT.com to ns1.Handyman-IT.com and ns2.Handyman-IT.com and you got a glue record setup (and the DNS got refreshed at your ISP) you aren't able to manage your DNS settings in godaddy anymore but you should use the DNS manager in your ISPconfig to create A records. Then you should be able to connect to your website.

If you got any problems you can contact me, just message me threw my profile.

 

I may have to do that... LOL....

Glue records are a sticky wicket with GoDaddy right at the moment. The are stating it would be easier / better to use their name servers or go with "premium" combining a local with one of theirs... Will PM you if more appropriate.

Thanks for all the help so far.

 

OK, just got off phone with GoDaddy - they are looking into the trouble with my DNS entries, says it looks good on my end, they can see my server up and running, just not sure why the records are not updating on their end. Glue records are not what they call them, essentially when you "register" your server with them and assign it as the DNS it on your IP it removes the hen / egg issues.

Now they are asking me if I need DNSSEC keys - to which I am not sure at all. From what I can read it is like a certificate or private key for the DNS servers. I am looking into how to create one, if needed. Seems like Linux has the ability to do so, or so it would seem using the dnssec-keygen command.