Designate IP for use as shared IP

[Techie-Micheal]

I'm having a hard time finding information on this, so hopefully I can get this worked out.

Problem:

I have 5 IP addresses allocated to me from my server provider. The first IP is to be used by SSH, DA, and the first NS. The second IP is to be used by the second NS. The third by the email server. And the fourth by the web server. The fifth IP will be miscellaneous. A game server or whatever. The fourth IP will be shared by all resellers and users to use name-based virtual hosting.

Possible Solution (nasty hack):

Modifying the custom DNS and Apache config files to point to the actual IP I want them to use will more or less give me what I want, yes? Is there a more elegant solution?

 

[nobaloney]

Your first need is the DirectAdmin default (but DA itself will respond on all IP#s on the server).

You can configure DA to use the first two IP#s as your first and second nameservers easily enough.

You can make a change to th exim.conf file so exim will only use the third IP#.

And you can setup every reseller and every user to use only the fourth IP#.

So you really shouldn't have to do any nasty hacks; only a simple one to exim.conf.

Jeff

 

[Techie-Micheal]

Thanks.

I run with no CP on my current server, and hack away and DNS and Apache and Exim and so on (have a pretty sexy setup, if I do say so myself), but I'm trying to make things a bit easier administration-wise with DA, and DA offers a few extra features for my users that I think they'll like.

I have no problem modifying sshd_config and exim.conf and so on to get them listen on specific IP addresses. I've done that already on my previous server (and encourage everybody to do that, since having services listening on all interfaces is a bad idea, IMO). I guess I wasn't clear enough, sorry. What I'm after is getting DA to see all of those changes, and most importantly, how do I tell it I have one specific IP address I want it to use for all sites created?

I created a reseller package, set the options as I wanted, and set that the reseller has 1 IP address. I go to create the reseller, and it says they have 4 free IP addresses. It also says that the reseller can create websites using the server IP as a shared IP, which is not what I want. I do see the option further up the page where it says Shared - Server, Shared - Reseller, and Assigned, but I can't figure out where to specify all of that, or what the Shared - Reseller means.

I realize these questions are probably basic, but I come from a world of no control panels (heck, when I purchased the current server, DA didn't even have a beta for Debian, which is my OS of choice). I'm a command line junkie.

 

[nobaloney]

As admin, under the IP Management section, unshare the IP#s you don't want the resellers to see.

I'm a command-line junkie myself, having run hosting businesses since early 1995 on an early Slackware distribution, and linux kernel version 0.99.

We had a 128k connection to the 'net, which was fast in those days; the local University only had 56k shared among the entire campus.

We used the model later made popular by 9Net Avenue; we had a simple database where we kept copies of everything the customer had in his/her setup.

When we took a call we first pulled up the setup on the screen, made the changes, and saved the new setup. At that point our program printed out a sheet with only the necessary changes to be made.

(We wrote our own database, using a 4GL language called DataFlex.)

It was extremely labor intensive. While at the beginning we offered shell accounts where our savvy customers could set up and control their own hosting, that resulted in a lot of support calls.

So I was very happy when the early appliances came out (I knew the folks who invented the Cobalt RaQs, and I used them since they made changes I required, with the introduction of the RaQ2.

When Cobalt discontinued the RaQ4 (I never did like either the xtr or the RaQ 550) I became a Plesk Gold Partner, and two years later discovered DirectAdmin. The rest, as they say, is history .

Jeff

 

[Techie-Micheal]

Thanks. But unfortunately, for now at least, I've dropped DA from the server. Partly because we were trying to figure out how DA works and getting it to do what we want and partly because the provider caused problems, we decided it best to just not use DA.

But thank you for the help.