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

[editor]

my tips make you to a millionare. Costs only some red greek wine for you. And the plesk-red panties are already here. ;-)

 

[MaRiOs]

Ok then give me a solution on how to setup an open source pptp server on my server cause my boss will kill me if i dont ;pppp

and ill send u 10 more bottles or red wine ;p

 

[editor]

I will give you another good tip:

If you are a provider - providerdomain.tld - with your client (clientdomainname.tld),
then try to avoid the following DNS-construction:

clientdomainname.tld
ns1.providerdomain.tld
ns2.providerdomain.tld

Use this solution:

Register a 2nd providerdomainname for you as a provider.
Use this domainname as the 2nd DNS-name. Then you make

clientdomainname.tld
ns1.providerdomain01.tld
ns2.providerdomain02.tld

You should also take care for the .TLD. Do not use both .TLDs as
.COM or .NET or .ORG. Try also to be very different there. The
best would be to use minimum one
ccTLD (=CountryCodeTopLevelDomain) for it, f.e.

clientdomainname.tld
ns1.providerdomain01.tld (in your case: .GR for Greece)
ns2.providerdomain02.tld (.NET)

Because of 2 different .TLDs, you can also melt providerdomain01
and providerdomain02 to one providerdomain, which means:

clientdomainname.tld
ns1.providerdomain.tld (in your case: .GR for Greece)
ns2.providerdomain.tld (.NET)

For a computer, the registry and the registration-center, an

EXAMPLE.GR
EXAMPLE.NET

are 2 different domainnames although both have the same name
"EXAMPLE". Some Plesk-users are from Belgium, Italy, Germany
or USA. They should just use their own ccTLD alike .BE, .IT,
.DE or .US.

If you understand this construction - which you can do with
Plesk by a very easy way, here...

clientdomainname.tld
ns1.providerdomain.cctld
ns2.providerdomain.tld (.NET)

..then try to consider about the next step. Try to avoid

ns1
ns2

It is better to give it a better name instead of this "wannabe-standard"
ns1 and ns2. Try to find out in which city and place this DNS-machine
is located.

For example, in your case, if you are located in Crete Islands
in Greece, then try to use

clientdomainname.tld
crete.providerdomain.GR (=ccTLD)
anothercityname.providerdomain.NET (=gTLD)

For example, if you backbone-connection goes from Crete
Islands in Greece to Rome in Italy, then use
"rome.providerdomain.NET". Another example would be, if your
Plesk-Server is not located in Greece. It's located in
Redmond, WA (USA), then use "redmond.providerdomain.gTLD
(.NET).

Background: Many hackers and many uncontrolled robots in the
internet always try to use the "wannabe-standard" with ns1
and ns2, because they always try at first the
"DNS-beginners". It is a theme about the security to protect
your DNS and your BIND.

Here again the overview with the final result:

-------------cut----------------
clientdomainname.tld
=================
yourcityname.providerdomain.ccTLD (f.e. .GR for Greece, .DE for Germany, .US for USA, etc.
anothercityname.providerdomain.gTLD (.NET)
-------------cut----------------

We can also talk about examples in the internet. You see then
very well, if a network-construction was done _professional_
or risky. Remember always this -cut-cut- from the lines above
and look to some examples with some comments by me:

MICROSOFT.COM
==============
NS3.MSFT.NET
NS1.MSFT.NET
NS5.MSFT.NET
NS2.MSFT.NET
NS4.MSFT.NET

= unprofessional.
1) If .NET will be down, the complete MICROSOFT.COM will be offline.
2) if MSFT.NET will be down, the complete MICROSOFT.COM will be offline.
3) They use the wannabe-standard ns1, ns2, ns3, ns4, ns5. Easy to hack.

IBM.COM
=======
INTERNET-SERVER.ZURICH.IBM.COM
NS.WATSON.IBM.COM
NS.ALMADEN.IBM.COM
NS.AUSTIN.IBM.COM

= unprofessional.
1) If the .COM will be down, the complete IBM.COM will be down.
2) If the IBM.COM will be down, the complete IBM.COM will be down.
3) A lilttle bit better than MICROSOFT.COM are the given names
to the DNS. They use "zurich, watson, almaden, austin". But it
is not perfect, because they all are totally dependent from the
IBM.COM.

CNN.COM
========
TWDNS-01.NS.AOL.COM
TWDNS-02.NS.AOL.COM
TWDNS-03.NS.AOL.COM
TWDNS-04.NS.AOL.COM

= unprofessional
If .COM or AOL.COM will be down, then http://www.cnn.com is offline.

SW-SOFT.COM
============
NS1.SW-SOFT.COM
NS2.SW-SOFT.COM
NS3.SW-SOFT.COM

= unprofessional
Same reasons like MICROSOFT.COM and IBM.COM.
The best one thing is, that if SW-SOFT.COM will be down, then
the Admin and TechZone of SW-SOFT.COM will not be able
anymore to update the registry, because they also use the
sw-soft.com for email.

Here again:

-------------cut----------------
clientdomainname.tld
=================
yourcityname.providerdomain.ccTLD (f.e. .GR for Greece, .DE for Germany, .US for USA, etc.
anothercityname.providerdomain.gTLD (.NET)
-------------cut----------------
ccTLD = CountryCodeTopLevelDomain (see also ISO 3166)
gTLD = GenericTopLevelDomain (.NET, .COM, .ORG, .INFO)

Originally posted by MaRiOs
Ok then give me a solution on how to setup an open source pptp server on my server cause my boss will kill me if i dont ;pppp

Point-to-Point Tunneling Protocol for creating Virtual Private
Networks (VPNs)? Oh, that's easy. What's the problem? For
what exactly do you need this?

 

[MaRiOs]

look what we want to do.
setup and run an open source pptp server, (like http://www.poptop.org/ )
and then when i create an new account at plesk, and give ssh access to a domain user then i want him automaticaly to have access to the VPN with tha same login/password he has for SSH.

Why do we need VPN for ? dont ask me..
I just have to do that

 

[MaRiOs]

ok the pptp server is UP and running,
and i did a connection through windows and its ok.

Now i have to solve only the problem about usernames and passwords.

take a look here : http://poptop.sourceforge.net/dox/redhat-howto.phtml
and here
http://poptop.sourceforge.net/dox/chap-secrets.txt

I've added to

# PPP CHAP secrets file.
# See pppd(1) for file format.

# Secrets for authentication using CHAP
# client server secret IP addresses
#username pptpd password *
i've added in this conf file this line :
myname pptpd mypass *

and it worked fine.
What i want to do is to make it retrieve automatically the login name and passwords tha users allready have from SSH.

 

[editor]

Originally posted by MaRiOs
look what we want to do.
setup and run an open source pptp server, (like http://www.poptop.org/ )

So, you want to install Poptop onto your Plesk 7.5.2 Fedora Core 2?
Or do you want to make your own PPTP-Project?

Originally posted by MaRiOs
and then when i create an new account at plesk, and give ssh access to a domain user

Yes, Plesk 7.5.2 allows this to domainusers. What's the problem?

Originally posted by MaRiOs
then i want him automaticaly to have access to the VPN with tha same login/password he has for SSH.

Well, I would suggest to talk about this special theme later.
Let's make - for the first - the first steps, see my lines before.

Originally posted by MaRiOs
Why do we need VPN for ? dont ask me..
I just have to do that

I really suggest to make this onto a mirror-server before
you try anything in the internet onto the real one Plesk-server.

 

[MaRiOs]

Yes, Plesk 7.5.2 allows this to domainusers. What's the problem?

--- The point is that we lock down from the firewall any external attempts to the ssh server,
and allow it only from VPN

 

[MaRiOs]

So, you want to install Poptop onto your Plesk 7.5.2 Fedora Core 2?
Or do you want to make your own PPTP-Project?

---- No i dont want to make my own project.
just modify this in a way that i dont have to get into that file each time and give a new user name and password manualy.
I want it to take the user/pass from where red hat or plesk stores them.

 

[Raymy]

Hi there again,

After trying everything I could imagine by now, my DNS-stuff ain't working properly and I really don't know what to do anymore

My server has been setup as stated before.

IP 20.20.20.19 -> www.mydomain.com (site is online, so must be working properly I assume)
IP 20.20.20.20 -> SHARED IP for domains... nothing works
IP 20.20.20.21 -> Exclusive IP, not in use yet
IP 20.20.20.22 -> ns1.mydomain.com
IP 20.20.20.23 -> ns2.mydomain.com

When I create even subdomains like forum.mydomain.com it ain't working.
So my question is? Do I need to configure something else in Fedora Core 1 perhaps? In files like named.conf or resolv.conf?
I am clueless at the moment.
Everything in PLESK is working properly, except subdomains (allthough creation works just fine) and newly added domains.

 

[Raymy]

Anyone?
I found out that webmail.mydomain.com, mail.mydomain.com and ftp.mydomain.com also ain't working, but that seemed logical to me, since it's just another subdomain.
They all have A records in PLESK, my Nameservers are properly working according to http://www.dnsreport.com/
The DNSREPORT showed me also that I had no reverse DNS entry for my MX record, so, for the tenth time I think, I requested for a Reverde DNS at my hosting provider. I don't expect it will solve the problems now, but, hey, ya never know.
The added mailboxes in PLESK are (properly) working, so don't know what this problem really means, even if it is a problem at all.

It's just the subdomains that won't and all newly added domains for some weird reason.

Hope someone has a bright idea, caus I am out of them