DA / FreeBSD / NAC.NET Problem

R

robg

Verified User
Joined
Sep 3, 2004
Messages
6
I have a server purchased from NAC/15-Minute-Servers and have FreeBSD 4.10 and DirectAdmin installed on it. NAC e-mailed me the list of IP addresses I have and they are as followed:

209.123.8.144 Server IP
209.123.181.99 Direct Admin
64.21.131.104 Additional Free IP Address
64.21.131.105 Additional Free IP Address
64.21.131.106 Additional Free IP Address
64.21.131.107 Additional Free IP Address
64.21.131.108 Additional Free IP Address
64.21.131.109 Additional Free IP Address
64.21.131.110 Additional Free IP Address
64.21.131.111 Additional Free IP Address

The 'Welcome E-mail' also said: "If you elected to install the DirectAdmin control panel, you will be assigned a single additional IP address only to be used for DirectAdmin. You should not run any services such as web, DNS or mail servers on this IP Address." So this IP address is 209.123.181.99.

Now DirectAdmin is running so if I goto Admin -> IP Management, it shows 209.123.181.99 as the 'server' IP since DA is running on that IP, and not 209.123.8.144. And the support at DirectAdmin said that all services in use by DA are binded to all IP Addresses, including the one DA is on (209.123.181.99). But it said to only run DA on the IP, and not any other services. I'm confused.

From what I see there's no mention of the main Server IP - 209.123.8.144 and I'm not sure what to do here. I'd just like to setup my box so it's 'black.xcage.net' (it's hostname) and run the website http://xcage.net/ off of it as well, but I don't know what to do about the IP info above.

Doing a ifconfig returns:

rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 209.123.8.144 netmask 0xffffff00 broadcast 209.123.8.255
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 209.123.181.99 netmask 0xffffffff
inet 64.21.131.104 netmask 0xffffffff
(all the way to 64.21.131.111...)

So the DA and Free IPs are on the Loopback, and I don't see what to do with the main IP 209.123.8.144.

Do you have any ideas? Sorry for the long post.

Thanks.
 
I don't know why NAC tells you that either, but my guess is that in order to have licenses available so they can install servers in 15 minutes, they assign IP#s in advance, one for each server, so they'll be able to order DA licenses in advance.

Then when you order a server, my guess is they add the other IP#s, which they intend you to use.

Looking at the netmask reporting, it looks as if your box is NOT on it's own private network, which adds credence to my theory.

I don't see any rason why you can't use .99 as your main shared IP#, but NAC may have a reason.

Have you asked them? Unless they specifically say you can't use .99 as a shared IP, then you can and probably should.

Based on the ifconfig output you posted, the server will use .144 as it's main IP#.

Jeff
 
jlasman said:
I don't know why NAC tells you that either, but my guess is that in order to have licenses available so they can install servers in 15 minutes, they assign IP#s in advance, one for each server, so they'll be able to order DA licenses in advance.

Then when you order a server, my guess is they add the other IP#s, which they intend you to use.

Looking at the netmask reporting, it looks as if your box is NOT on it's own private network, which adds credence to my theory.

I don't see any rason why you can't use .99 as your main shared IP#, but NAC may have a reason.

Have you asked them? Unless they specifically say you can't use .99 as a shared IP, then you can and probably should.

Based on the ifconfig output you posted, the server will use .144 as it's main IP#.

Jeff
Click to expand...

thanks for the reply, i deleted the other thread.

i e-mailed them and asked about it, but no reply yet. if they say i can't, then what would i do? da binds everything to all ips, so www/ftp/etc would already be running on DA's ip that they said it "cant be used for". i dont see how i can't use it, when da is running on that ip.

is there a point to the main server IP then? i dont see any, since everything will use the DA IP... this is confusing :confused:
 
Just don't YOU use it for anything. In other words don't use the DA IP in any DNS zone files.

Why would they have a separate Server IP# then?

My guess is because they may not monitor the DA IP# for usage. But it's just a guess.

The server will be reporting the Server IP# and not the DA IP# for outgoing services.

Jeff
 
well this is what 15min said about the ip:

We don't suggest running any services on your directadmin IP, but you can do it. Now the main reason that we don't suggest it is that IP is and will always be tied to your directadmin license. So if you decide to switch control panels down the road you're going to have to renumber. Also if that IP gets DOS'd and we have to nullroute it for a while you won't be able to admin your box.
 
so what do i do.. if they dont suggest running services on the da ip.. i don't get it, all services are running on the IP automatically since da is binded to run off that IP... :confused: and if i want to set the default website in DA under admin, it uses the DA ip to do it :mad:
 
robg said:
so what do i do.. if they dont suggest running services on the da ip.. i don't get it, all services are running on the IP automatically since da is binded to run off that IP...
Click to expand...
Just don't set up any sites on that IP#. The server, by default, will NOT use that IP# as the default IP# for outgoing data. And if you don't set up any sites on that IP#, it won't use it for incoming data either.

Should you give he DA IP# to your clients for login purposes? That's up to you. You can if you want.
and if i want to set the default website in DA under admin, it uses the DA ip to do it
Click to expand...
If you use the default user account, yes it will. And NAC has already said you can, but if you do, and if you ever choose another control panel, then they'll take that IP# away from you and you'll have to renumber your site. I don't see that as a big issue. Having to renumber all your clients sites I'd see as a big issue, but not having to renumber only your own.

Or you can go into the reseller panel and set up a new site there, and make that your main site.

Which is probably what I'd do.

Jeff
 
jlasman said:
Just don't set up any sites on that IP#. The server, by default, will NOT use that IP# as the default IP# for outgoing data. And if you don't set up any sites on that IP#, it won't use it for incoming data either.

Should you give he DA IP# to your clients for login purposes? That's up to you. You can if you want.

If you use the default user account, yes it will. And NAC has already said you can, but if you do, and if you ever choose another control panel, then they'll take that IP# away from you and you'll have to renumber your site. I don't see that as a big issue. Having to renumber all your clients sites I'd see as a big issue, but not having to renumber only your own.

Or you can go into the reseller panel and set up a new site there, and make that your main site.

Which is probably what I'd do.

Jeff
Click to expand...

thanks, ill try it out :)

one question, im not sure if this is a bug.. if i go into IP Managment, it only shows one ip the DA ip, but when I add one of my free ips such as 64.21.131.105, it says:

Error with your request

Details

IP 64.21.131.105 already exists on eth0

but then I just go back to ip managment, and the IP is added to it, so it goes through..

not a big deal :eek:
 
DA tried to add the IP# to the list of IP#s the server should answer on, but it found the server was already set to answer to it.

I don't know why you got the error, though.

Jeff
 
You must log in or register to reply here.
Back
Top