How to create resellers with sheard IP ??

Hello,

At the "Create Reseller" screen, you select:

Shared - Reseller's IP

This will take one of his IP's, make it shared and put him on it :)

John
 
I did that but it shows

Error Creating User xxxxxx

Details
You have not given the reseller any IP's. Unable to create an assigned IP domain or any nameservers without any
 
As admin, go to IP Manager. Then select the IP you want to give to that reseller, and change the drop down menu to the name of the reseller. Then click Assign To.

Then go back and create the reseller. I /think/ that's what you're looking to do.
 
Do you want more resellers on the same ip, or do you want 1 reseller on 1 ip with the domain on the shared ip?

Because if you want to put all your resellers on the same ip that will require you to either choose the main server ip, or you have to edit the ip.list file in /usr/local/directadmin/data/users
 
If I choose the main server ip my resellers can not create accounts it shows (You must first own an IP) ??

please help.....
 
So you have ensured that the box "share main server ip" was on when you created those accounts?

If so, there seems to be a problem with the ip.list file. SSH in as root and go to /usr/local/directadmin/data/users/<username>/ip.list and see if there's anything in that file

Code: 
cat /usr/local/directadmin/data/users/<username>/ip.list
 
Hello,
I did that but it shows

Error Creating User xxxxxx

Details
You have not given the reseller any IP's. Unable to create an assigned IP domain or any nameservers without any
Click to expand...
Well you need to assign him at least 1 IP in the package :)
Else, DA won't have any IP's to pick from to set as shared.

John
 
Ok my it show this on www.dnsreport.com



ERROR: One or more of your mail server(s) have no reverse DNS (PTR) entries (if you see "Timeout" below, it may mean that your DNS servers did not respond fast enough). RFC1912 2.1 says you should have a reverse DNS for all your mail servers. It is strongly urged that you have them, as many mailservers will not accept mail from mailservers with no reverse DNS entry. You can double-check using the 'Reverse DNS Lookup' tool at the DNSstuff site. The problem MX records are:
30.230.45.66.in-addr.arpa [No reverse DNS entry (rcode: 3 ancount: 0)]
 
If you have dns authority over the reverse lookup, then you'll need to add the reverse lookup to the /etc/named.conf.

John
 
Alright :)

A reverse IP lookup is the opposite of a domain lookup. For example the main purpose of the who internet domain name system (dns) is to translate a domain (domain.com) to an IP (1.2.3.4) which is required for your computer to find a webserver on the internet. Now email program often do a security check, and try to figure out the domain FROM the IP that's connecting to make sure the sender is who they say they are. This is a called a reverse IP lookup.

domain lookup:
domain.com -> 1.2.3.4

reverse ip lookup:
1.2.3.4 -> domain.com

Now, so setup a reverse IP lookup, it has to be done manually becuase it's only has to be done once per IP, and much of the time, datacenters do it for you, so you don't even need to worry about it.

When time becomes available, we'll get DA to do it automatically for people, but it doesn't exist at the moment.

For the case that you do need to do it yourself, you can do the following:

edit /etc/named.conf and add:
Code: 
zone "4.3.2.1.in-addr.arpa" IN {
        type master;
        file "/var/named/hostname.db";
};
Note that the numbers for the IP are backwards in that file. Then edit /var/named/hostname/db, and set:
Code: 
$TTL 0
@       IN      SOA     ns1.domain.com.      root.domain.com. (
                                                2003082300
                                                7200
                                                3600
                                                1209600
                                                86400 )

        NS      ns1.domain.com.
        NS      ns2.domain.com.
        PTR     domain.com.
The ns1/ns2 values should be any nameserver that you have on your machine. root.domain.com is an email address ([email protected], but replace @ with . ) The domain.com beside the PTR value is the actual value that is returned. Generally this will be set to your server's hostname, but ultimately, it's the value you want the reverse IP to return.

Save that, then just type
Code: 
service named reload
and that should load in the new settings. You can test your new reverse ip to make sure that it's working by typing:
Code: 
dig -x 1.2.3.4 @127.0.0.1
This willl ask your own copy of named what it's returning. Once that's working, it's out of your hands. As mentioned before, some datacenters have control of the reverse IP, so anything your create might not have any effect.

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