I just bought my second VPS server. Both VPS's have Plesk installed. I have only one domain name for my "web hosting company" and I want it to remain that way, so I named the first VPS vps1.mydomain.com and the second vps2.mydomain.com. Until now, when I registered a new domain name, I used the nameservers ns1.mydomain.com and ns2.mydomain.com, which both point to my old VPS.
And finally the question: what do I do now, DNS-wise? Do I use another hostname, i.e. ns3.mydomain.com, which will point DNS to the new VPS and use this address when registering a domain that I want hosted in the new VPS? Isn't there some other, more delicate way of managing this?
I have another question: is there any point in changing ns2.mydomain.com to point to the new VPS and somehow (how?) sync the two DNS servers? I mean, if the primary DNS server dies, so will the sites hosted on it, so I don't really need the DNS services to work!! I'll have more serious problems to deal with... 8-) Any suggestions are welcome.
OK, I'll rephrase my question as I think I might have not been clear enough.
The situation is the following:
nameservers: ns1.mydomain.com, ns2.mydomain.com
has an A record: vps2.mydomain.com to point to the other VPS
Until now, when I register a new domain name, I set it up with ns1.mydomain.com, ns2.mydomain.com in order to point to the first VPS.
What do I set up now, if I want a domain to be hosted to the new VPS?
In order to do what you suggest in Plesk, I'd have to set up the domains that I want hosted on the second VPS twice. Once on the "secondary" VPS (this is where it will be hosted) and once on the "primary" VPS (in order to set it as the secondary DNS server for that domain). Is this correct? Isn't there a more "delicate" way?
Hi, thanks for the answer, but what purpose would that server? I mean what good is having a working secondary DNS server if the actual webserver is dead?
The use of a secondary nameserver is that it represents the life of your domain name. When your primary site and nameserver go dark, then without a functioning secondary/slave nameserver, remote clients get the impression that the domain name is no longer in use. It's hard to imagine all the different implications this may have, but one sure one is a speedy removal of mailing list subscriptions to users at the now dark domains.
With a secondary/slave, remote clients see that the domain is alive, but that its webserver, or mailserver, are temporarily out of order.