ISPConfig — Build and Configure

If you haven't already...
Set up an Affiliate Account or Set up a Small Business account.
Posted on November 23, 2017 by admin under ISPConfig
Leave a comment

Following this, complete the CentOS 7.3 Minimal Server process to update and install required packages. Once this is done, follow the The Perfect Server for the ISPConfig3 portion.

Now that we have a working ispconfig3 system, we can begin configuration. In my environment there are some peculiarities which I will list as we go along.

First off, there is a little housekeeping we want to do to help in managing the user accounts created by the server. Follow the procedure in ISPConfig — Main Config — Prefix’s post, it will give you the changes and the change procedure.

Now that the housekeeping is complete, what do we want to do first.

Add ISPConfig users

Although Client and or reseller accounts are not required and in this dissertation, It is a good logical place to start, especially since we defined our prefixes above based on client id’s.

Resellers do exactly that, resell the services. Although they are designed for use by separate companies, you could define your sales agents as resellers and use the information to determine payment.

Clients can be created by the admin or resellers. Clients are restricted to domain activities and cannot create new clients.

Feel free to create a reseller, but definitely create at least one client. We will be doing our work as administrator, but as mentioned a couple of times, we rely on at least one client for this discussion.

See the ISPConfig — Add Reseller post to setup a reseller and ISPConfig — Add Client to add a client.

Reseller, by default, do not have limit constraints.

Setup DNS

We will add our DNS manually. The wizard is fine if you choose. You can also use the import, although, I did have some issues importing my dns, so I think for smaller zones it is sometimes easier to just do it manually.

We will have a single zone named of course, quantumleaps.com. This zone will have the following A records.

  • mail
  • ns1
  • ns2
  • quantumleaps.com. (a domain entry for default purposes)
  • www (Not strictly needed, but i like to have them just cause.

We will then setup an MX record and two NS records.

To complete this procedure see the ISPConfig — Setup DNS Zone.

Setup Email Services

Now that we have DNS setup, our next move will be to setup email services for the domain.

To do this see the ISPConfig — Setup Email Domain for the procedure.

If you didn’t already go through the procedure, please see ISPConfig3 — Aamavisd –Can’t open PEM file

Add an Email client mailbox

Now we want to create a new email mailbox. To do so, follow the ISPConfig — Add new Mailbox procedure. I recommend you create two mailboxes as we use them for testing in the Validate Email is Working Properly procedure which is referred to below.

Lets Back up a little

Earlier, we setup DNS, and now we have setup an email domain. We also enabled DKIM signing which is great.

One item we omitted however was an SPF record. SPF and DKIM keys provide authentication and message verification for received emails. See ISPConfig3 — Add SPF Record for the procedure. Once complete, we will move along.

Setup a Site

We are finally ready to create a new site. Sites are how you provide your clients with a web presence. More specifically, a site provides the pages you access via a browser.

To setup an initial site, see the ISPConfig3 — Add Site for the procedure.

We now have a site, but no method of managing it. To update your site, you need an FTP account for the site. This is where the settings we modified in the ISPConfig — Main Config — Prefix’s procedure come in handy. When i create ftp accounts to access sites, I like to use the name admin. Consider a scenario where we have a single client with two sites. The first site could be 1admin, but the second would need to be something different…say 1admin1 or something else insane like that. Account complexity is relational to the number of accounts.

To limit the complexity, we use a prefix of C[CLIENTID]D[DOMAINID] for the ftp account names. Now we can have the the same, or close, name for all of the site admin accounts with only the domain prefix changing. Now my account id’s are c1d1admin and c1d2admin… which at least helps. So keep this in mind as you go throught the ISPConfig3 — Add new FTP-User procedure.

Review

We have gone through several procedures and Whew, are my fingers tired. Seriously though, We have setup DNS, Email and created our web site. You should now be able to do the following tests for verification.

  1. Validate DNS is Working Properly
  2. Validate Email is Working
  3. WWW — Point your browser to the system using the system name. Ensure you receive the default test page.
    • At this point in the process, use HTTP rather than HTTPS.

You should now have a fully functioning system.

There’s still a lot left to do, but we will do those things in other articles.

 

Leave a Reply

Please Login to comment
  Subscribe  
Notify of