NoBaloney2
NoBaloney Internet Svcs.
Please see this old thread for referene:
http://forum.directadmin.com/newreply.php?do=newreply&p=200657
Is this the only way to do it?
I've got a totally messed up set of ip# assignment files.
We had a server crash, so we restored to a new one. But we used a new IP# for the new server. Probably a mistake, because we're having lots of problems.
We created the new server on it's own ip# (.80).
Then we added to it all the IP#s previously assigned to the broken sever, including the old server IP#, #66.
First we restored all the resellers, selecting for them to use the IP# in the backup. We did verify that all the IP#s in the backup were active and free on the new server.
When the resellers were restored we may have made another mistake; we didn't check to see to which IP# the resellers had been restored. This probably meant (we can't be sure) that all of the resellers were created with the server IP# (.80).
We didn't check so I can't be sure, but I can tell you that's the way they are now.
Then we restored all the users for all the resellers (one pass), again selecting for them to use the IP# in the backup.
They appear to have all been restored to the IP# in the backup.
But at the admin level and at the individual resellers logins the IP# assignments are totally wrong. IP#s which were supposed to be marked as shared by the resellers aren't. They ended up instead being assigned to one of the restored users, as assigned. And as a result the resellers can't create new users; they haven't got free IP#s.
Is there any way to fix DirectAdmin's reporting of which IP#s are whose, and whether or not they're shared or server IP#s, depending on which IP#s are actually assigned (because the assignments are correct)? If not, then how can I do it by hand? This server has 27 resellers on it; I really don't want to make any mistakes.
Thanks.
Jeff
http://forum.directadmin.com/newreply.php?do=newreply&p=200657
Is this the only way to do it?
I've got a totally messed up set of ip# assignment files.
We had a server crash, so we restored to a new one. But we used a new IP# for the new server. Probably a mistake, because we're having lots of problems.
We created the new server on it's own ip# (.80).
Then we added to it all the IP#s previously assigned to the broken sever, including the old server IP#, #66.
First we restored all the resellers, selecting for them to use the IP# in the backup. We did verify that all the IP#s in the backup were active and free on the new server.
When the resellers were restored we may have made another mistake; we didn't check to see to which IP# the resellers had been restored. This probably meant (we can't be sure) that all of the resellers were created with the server IP# (.80).
We didn't check so I can't be sure, but I can tell you that's the way they are now.
Then we restored all the users for all the resellers (one pass), again selecting for them to use the IP# in the backup.
They appear to have all been restored to the IP# in the backup.
But at the admin level and at the individual resellers logins the IP# assignments are totally wrong. IP#s which were supposed to be marked as shared by the resellers aren't. They ended up instead being assigned to one of the restored users, as assigned. And as a result the resellers can't create new users; they haven't got free IP#s.
Is there any way to fix DirectAdmin's reporting of which IP#s are whose, and whether or not they're shared or server IP#s, depending on which IP#s are actually assigned (because the assignments are correct)? If not, then how can I do it by hand? This server has 27 resellers on it; I really don't want to make any mistakes.
Thanks.
Jeff