How do you assign domains to IPs?

[jiri2]

http://reseller.site-helper.com/ip.html doesn't help. I would like to know

Whether the nameserver can be the name of any domain, of a domain I don't own, and whether there's a problem if the domain of the nameserver is the domain name of one of the domains I want to setup on directadmin.

What netmasks do I use for the additional ''free'' IPs. The server IP is on 255.255.255.248. Am I doing something wrong if I let the free IPs be on netmask 255.255.255.0?

I would like to know how to assign the domain to the additional IP. It keeps resolving to the server IP.

And I would like to know why the server IP claims to have a user, even though I don't know what it's talking about and its ''reseller'' column is blank. And why the reseller for the additional ''free'' IP is ''admin'', even though its user column is blank so seemingly claims to have no users.

Thanks in advance for any help.

 

[nobaloney]

Some of your questions have nothing to do with DirectAdmin. I shall try to answer them anyway.

Whether the nameserver can be the name of any domain, of a domain I don't own, and whether there's a problem if the domain of the nameserver is the domain name of one of the domains I want to setup on directadmin.
To set up a nameserver you must have control of both the domain and the zone file for the domain. It doesn't matter whether it's on your DirectAdmin server or not. If it's not you simply set it up on DirectAdmin as a virtual nameserver. But that's after it's set up at your registrar and in the main zone file for the domain it's on.

For example, to create ns1.example.com, first you go to the registrar where you've registered example.com, and set up the nameserver host records. This is NOT the same as assigning a nameserver for example.com; if you don't know how to do it at your registrar, then ask their tech support, or transfer your domain registration to me, and then I can help you with it .

Then you edit the zone file for example.com (wherever it's located) to add A records for the ns1.example.com and ns2.example.com. Then restart your nameserver software if necessary. (If you're not sure, do it; it won't hurt.)

Then add the nameservers inside DirectAdmin as virtual nameservers.

If you're using IP#s hosted on your DirectAdmin servers make sure the IP#s are added to DirectAdmin and respond to nameserver requests.

What netmasks do I use for the additional ''free'' IPs. The server IP is on 255.255.255.248. Am I doing something wrong if I let the free IPs be on netmask 255.255.255.0?

In short, yes. Ask your IP# provider what the correct netmask is if you aren't certain. Generally it's the same as what DirectAdmin shows for the main shared IP#.

I would like to know how to assign the domain to the additional IP. It keeps resolving to the server IP.

You don't assign the domain to the IP#; you assign the IP# first to the reseller, then to the user, then to the domain if you've got multiple IP#s per user.

And I would like to know why the server IP claims to have a user, even though I don't know what it's talking about and its ''reseller'' column is blank. And why the reseller for the additional ''free'' IP is ''admin'', even though its user column is blank so seemingly claims to have no users.

If you're not sure, delete them and start over. You can't delete the main shared IP# (the server IP#); if you've got a domain at the user level of the admin control panel, that could be the user. To know with certainty I'd have to look at your system. I charge for logging into your system to help you. I can fix everything. If you're interested, please feel free to email me (email address below in my siglines).

Jeff