Assigning Server IP the status of "server" through DA?

[whitehat]

I have yet to find this question answered anywhere in the DA forums..... and Google was not my friend on this issue.

This issue has nothing to do with DNS, ftp, or anything else -it's strictly an IP issue.

In DA, when looking at 'IP Manager' at the admin level or 'IP Configuration' at the reseller level, one can see that the admin (me) has IP's assigned to a reseller, who in turn assigns those IP's to users. Some IP's are owned, some are shared, and some are free. Currently, there are 16 IP's on my server. My DA license IP is that of my server IP. Not one IP was assigned as 'server', which was really messing up ftp.

Through ssh, I was able to manually change the file /usr/local/directadmin/data/admin/ips/69.61.61.194 (the IP of my server & DA License) to assign to it the status of 'server'.

There is a wonderful picture in the outdated help files (http://admin.site-helper.com/ipman.html) of how the IP config should look; however, I have found NO documentation anywhere as to HOW to have DA do it for me/us through the panel.

This issue was addressed in a question two years ago (http://www.directadmin.com/forum/showthread.php?p=30753#post30753) but was never answered.

John from DA in this post from December, http://www.directadmin.com/forum/showthread.php?p=88602#post88602 , also clearly states that the status of the Server IP needs to be 'server'.... but he did not state how to accomplish that task through DA.

So, redundantly, I ask redundantly - Apart from a manually file edit/change through ssh, does anyone know how to set the status of the server ip to 'server' through the DA panel?

 

[nobaloney]

When DA installs itself it should install it's first IP# as the server ip.

I wonder how this happened.

Jeff

 

[whitehat]

Thanks, Jeff - your answer makes sense and now I understand what happened.

Immediately after my server was set up and with the install of DA (over two years ago), we found that there was a problem with the initial block of IP's (not a DA issue -an issue with old delegation on that IP space). So my provider allocated an entirely new block for me, which required that the all of the old IP numbers be deleted and that the new ones be added.

In as much as this all happened right from the start, I never did notice how DA had set the status of the old IPs immediately after the install but before the new IP allocation.

As such, and never having seen the server IP as having the status of 'server', I never recognized that there was a problem or nor did I comprehend the impact it has on any of the potential consequences (such as ftp issues, shared IP home pages) because of the lack of having an IP with the status of 'server'. Amazing that it has taken me this long to detect these issues.

A complete change/reallocation of IPs for a server is probably highly unlikely and rare for most people, but this possibility does indeed exist, as evidenced by the experience I just shared.

Based upon this scenario, it would seem to me that an option probably ought to be in place in DA to allow an admin to assign/reset the server IP status in the event that this situation occurs.

Or is my experience really that rare? Just wondering.