• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

How can i start a 2nd DNS server through Plesk's panel ?

M

MaRiOs

Guest
I need to start a second DNS server in another ip.
For example if my domain is www.mydomain.com and my nameserver is ns.mydomain.com i want to start a second service in which the ns will be ns2.mydomain.com and it will have a new ip that ill give to it.

I want to do this through the panel not manualy through the shell of Red Had.

Any suggestions ?
 
Originally posted by MaRiOs
I need to start a second DNS server in another ip.
For example if my domain is www.mydomain.com and my nameserver is ns.mydomain.com i want to start a second service in which the ns will be ns2.mydomain.com and it will have a new ip that ill give to it.

I want to do this through the panel not manualy through the shell of Red Had.

Any suggestions ?



server --> Server Administration --> ip-adresses

After it, you have added 2 ip-numbers which should become
DNS. The final result should be following:

mydomainname.tld
ns1.mydomainname.tld
ns2.mydomainname.tld

STEP 1
======
So, for the first, go to

mydomainname.tld
General --> domains ---> mydomainname.tld

Domains > mydomainname.tld >
DNS zone for the domain mydomainname.tld is a master DNS
server

Add record type (Add a DNS record)

ns1.mydomainname.tld. A 111.111.111.1
ns2.mydomainname.tld. A 111.111.111.2
(Note: There must be a "point" behind the tld!!!)
(Note: 111.111.111.X is only an example. Use your both
different ip-numbers please)

Save it. This means, that these domainnames

ns1.mydomainname.tld and
ns2.mydomainname.tld

can be resolved now onto this server-machine. This is one of
the most important thing.

STEP2
======
Every other domainname can have now ns1.mydomainname.tld and
ns2.mydomainname.tld as DNS. To avoid, that you must always
manual type this in each domainname-section, go to your
DNS-template.

Server --> Server Administration --> DNS

[Add New Records] and it should be there then

<domain>. NS ns1.mydomainname.tld
<domain>. NS ns2.mydomainname.tld
(Note: There must be a "point" behind the tld!!!)

This means now following: Everytime, if you add a new
domainname to your PLESK-server, it will add everytime
automatically the

newdomain.tld. NS ns1.mydomainname.tld
newdomain.tld. NS ns2.mydomainname.tld

Everytime, if you register a new domainname, this means,
that you can always use just ns1.mydomainname.tld and
ns2.mydomainname.tld. The domain-registry is only a
database, which should explain a computer, which DNS can
resolve a domainname. It knows then, that
ns1.mydomainname.tld and ns2.mydomainname.tld must be asked.
And ns1.mydomainname.tld and ns2.mydomainname.tld do know
very well whats going on with "domainname.tld".

HTH!
editor
 
Thank you my friend i ll test it as soon i ll have my second IP.

What version of Plesk do u have ? cause the menus seem a little different. I user 7.5.2 reloaded.
 
Originally posted by MaRiOs
Thank you my friend i ll test it as soon i ll have my second IP.

One of the problem is, that many providers and Plesk-Resellers
do not allow to have more than 1 IP-number. I dont know, if
you have the luck to get more than 1 IP-numbers (which
provider do you use? Maybe we will change one of our
Plesk-Server to another provider. We re still searching).

A good way would be to have 3 IP-numbers.

1 IP-Number for all your domainnames (exclusive or shared)
1 IP-Number for your ns1.mydomainname.tld
1 IP-Number for your ns2.mydomainname.tld

Of course, you can also do it with only 2 IP-Numbers, no problem.

If you want to do it very professional, then give each domainname
an own IP-Number. The effect in the search-machines
for each domainname is gigantic.

Originally posted by MaRiOs
What version of Plesk do u have ? cause the menus seem a little different. I user 7.5.2 reloaded.

My description before talks about Plesk 7.5 Reloaded and 7.5.2
Reloaded, runninng onto Linux. It is anyhow the same way
since Plesk 5.x.
 
our server is based at http://www.serverbeach.com/
im not sure how we will get the second ip ,cause im only an employee.
My superior will do that request from them.
I'll notify you with the completetion of the task.
 
Originally posted by MaRiOs
our server is based at http://www.serverbeach.com/
im not sure how we will get the second ip ,cause im only an employee.
My superior will do that request from them.
I'll notify you with the completetion of the task.

It depends where you are located. IP-numbers can be ordered

Europe
http://www.ripe.net/

North- and South-America
http://www.arin.net

Asian Pacifician
http://www.apnic.net

Africa
http://www.afrinic.net/

Latin-America
http://www.lacnic.net/en/

See also http://www.iana.org/ipaddress/ip-addresses.htm

Or you just ask your provider/backbone-provider to forward
some unused IP-numbers to your PLESK-server.

We had 256 IP-Numbers running directly via RIPE.NET.
You can also call such IP-Numbers "european ip-numbers".
But with the moving from Europe back to USA, we were not
allowed also to move our IP-Block to USA. We have to order
a complete new IP-Block at ARIN.

http://www.arin.net/education/end_user/index.html

Our problem is following: Plesk 7.5.2 allows you to add
255 IP-numbers, but the PLESK-reseller does not allow this.
The PLESK/SW-Soft itself have problems to fix this abusing.
We have 25 dedicated servers and each server should get
3 IP-numbers. The rest of the IP-numbers which are not used
can be ordered extra by a client. It is not expensive, it costs
about 5 USD.
 
Originally posted by editor
It depends where you are located. IP-numbers can be ordered

Europe
http://www.ripe.net/

North- and South-America
http://www.arin.net

Asian Pacifician
http://www.apnic.net

Africa
http://www.afrinic.net/

Latin-America
http://www.lacnic.net/en/

See also http://www.iana.org/ipaddress/ip-addresses.htm

Or you just ask your provider/backbone-provider to forward
some unused IP-numbers to your PLESK-server.

We had 256 IP-Numbers running directly via RIPE.NET.
You can also call such IP-Numbers "european ip-numbers".
But with the moving from Europe back to USA, we were not
allowed also to move our IP-Block to USA. We have to order
a complete new IP-Block at ARIN.

http://www.arin.net/education/end_user/index.html

Our problem is following: Plesk 7.5.2 allows you to add
255 IP-numbers, but the PLESK-reseller does not allow this.
The PLESK/SW-Soft itself have problems to fix this abusing.
We have 25 dedicated servers and each server should get
3 IP-numbers. The rest of the IP-numbers which are not used
can be ordered extra by a client. It is not expensive, it costs
about 5 USD.

My superior said he has to order from Arin,and that its difficult to give you a never used before ip.

How do u use resellers on your server ?
u create clients with many privileges ? or there is an mod or add on to create resellers ?
 
Originally posted by MaRiOs
My superior said he has to order from Arin,and that its difficult to give you a never used before ip.

How do u use resellers on your server ?
u create clients with many privileges ? or there is an mod or add on to create resellers ?

There are different ways to do it. A client can be the root
of 1 complete dedicated server (running Plesk). This
dedicated server has 3 IP-Numbers.
1 IP-number for domainname(s) of the client.
1 IP-number for ns1.clientdomainname.tld
1 IP-number for ns2.clientdomainname.tld

These 3 IP-numbers can be added in the Plesk-System.
It will already done by us, so the client has no extra-work.
Thats all. And the client as the root can create reseller-accounts
or whatever the client wants to do with the dedicated server.

Another way is, that the client does not need a complete
dedicated server - as a root with 3 IP-numbers. In such a
case, it would be enough just to give the client a reseller-
account.

Note: With each IP-number, you can run about 10.000 domainnames.
 
Originally posted by editor
There are different ways to do it. A client can be the root
of 1 complete dedicated server (running Plesk). This
dedicated server has 3 IP-Numbers.
1 IP-number for domainname(s) of the client.
1 IP-number for ns1.clientdomainname.tld
1 IP-number for ns2.clientdomainname.tld

These 3 IP-numbers can be added in the Plesk-System.
It will already done by us, so the client has no extra-work.
Thats all. And the client as the root can create reseller-accounts
or whatever the client wants to do with the dedicated server.

Another way is, that the client does not need a complete
dedicated server - as a root with 3 IP-numbers. In such a
case, it would be enough just to give the client a reseller-
account.

Note: With each IP-number, you can run about 10.000 domainnames.

Look we have only 1 dedicated server,and we want to sell "reseller" accounts to others.
For e.g. a reseller accoun with 1 giga so that the reseller can sell accounts of 50mb or whatever to his clients.
The question is .....
Can the reseller (as he is not root) create in his account simple users and give them panel access ?


If you dont understand (im not Greek so my english ****) give me your email and ill try to explain u further.
 
> Look we have only 1 dedicated server, and we want to sell
> "reseller" accounts to others.

No problem.
https://www.domainname.tld:8443/
Login as admin (=root).
Create a reseller-account.
Make it clear about the limits (f.e. 1 GB webspace, 10 GB Traffic).
To avoid, that you have everytime "manually" to setup a reseller,
you can also do it easier with the reseller-template.

The reseller can then login to https://www.domainname.tld:8443/
with his own username/password. After login, he will then see a
list of his domainnames. The reseller will not see the domainnames
of other resellers. Each reseller will only see his domainnames
and the domainname of the reseller's client.

> For e.g. a reseller accoun with 1 giga so that the reseller
> can sell accounts of 50mb or whatever to his clients.

Yes. The clients of the reseller can also login to

https://www.domainname.tld:8443/

The clients will use

Username: clientdomainname.tld
Password: The password of the client.

Alike you see,

- the admin (=root) can login to https://www.domainname.tld:8443/
- each reseller can login to https://www.domainname.tld:8443/ with its own username/password
- each domainname-client can login to https://www.domainname.tld:8443/ with its own username/password.

> The question is .....
> Can the reseller (as he is not root) create in his account
> simple users and give them panel access ?

Yes.

And all what you do there as a root/admin, you can use

ns1.yourdomainname.tld
ns2.yourdomainname.tld

If you have these both DNS, you can also allow a reseller to
use

ns1.resellerdomainname.tld
ns2.resellerdomainname.tld
which are mapped to your IP-numbers.

HTH!
 
Hi there,
I followed the instructions from 'editor' and 'fixed' the template in PLESK on my server with the admin-account.
Can you tell me if the DNS-template as shown in the attachment is correct for 2 DNS servers ?

Thank you.

pic.php
 
are these 2 IP-Numbers of the DNS on the same server-machine or are these 2 IP-Numbers "outside" of the Plesk-Server?

This template might work for a Plesk-Server with 3 IP-Numbers whereas all these 3 IP-Numbers are exact on the same Plesk-Server-Machine.
 
Originally posted by editor
are these 2 IP-Numbers of the DNS on the same server-machine or are these 2 IP-Numbers "outside" of the Plesk-Server?

This template might work for a Plesk-Server with 3 IP-Numbers whereas all these 3 IP-Numbers are exact on the same Plesk-Server-Machine.
Yes, the machine has a total of 5 IP's.
The base IP (example: 20.20.20.19) is used for the machine itself (exclusive).
And the 2 other IP's as seen in the attachment (20.20.20.20 & 20.20.20.21) are also exclusively used.
The 2 remaining IP's are going to be shared IP's.
 
Okay, thank you for the confirmation :)

I requested a Reverse DNS at my hosting provder, so in a few days it should be working, including subdomains.
 
Originally posted by Raymy
Yes, the machine has a total of 5 IP's.
The base IP (example: 20.20.20.19) is used for the machine itself (exclusive).
And the 2 other IP's as seen in the attachment (20.20.20.20 & 20.20.20.21) are also exclusively used.
The 2 remaining IP's are going to be shared IP's.

wonderful. May I ask you which provider you have? URL?

I would use

20.20.20.19 = base IP for the machine itself, you re the provider
20.20.20.20 = anonymous FTP
20.20.20.21 = ns1.providerdomain.tld
20.20.20.22 = ns2.providerdomain.tld
20.20.20.23 = shared IP for clients and their clientdomainnames.tld

one clientdomainname.tld has provider DNS
ns1.providerdomain.tld
ns2.providerdomain.tld

if the clientdomainname.tld want his own DNS
ns1.clientdomainname.tld
ns2.clientdomainname.tld
then the client should pay for it, f.e. 5 USD/month. ;-) For you,
there are no costs because you just only map

ns1.clientdomainname.tld to 20.20.20.21
ns2.clientdomainname.tld to 20.20.20.22
 
Noproblem, I'll give you compliments and you'll give me answers :D :p
 
Back
Top