For example, if I have setup ns1.domain.com and ns2.domain.com on a server. Then I want to get another server and setup ns3.domain.com and ns4.domain.com to point to the new server. Is this possible just by adding new host records (ns3/ns4) on domain.com?

Originally posted by twrs
Is this possible just by adding new host records (ns3/ns4) on domain.com? Not sure what do you mean by that?

If you want to make ns3 primary/ns4 secondary, you can just setup ns3/ns4 on the second server the same way you set ns1/ns2 on the first server.

Or do you want both of them to be secondary of ns1 and update the records from ns1 automatically?

Originally posted by dabystru
Not sure what do you mean by that?

If you want to make ns3 primary/ns4 secondary, you can just setup ns3/ns4 on the second server the same way you set ns1/ns2 on the first server.


Yes, I want to make ns3.domain.com primary and ns4.domain.com secondary on the second server. Is this as easy as I thought?

What he means is that if his server1 goes down if that happens, then his site will show on server 2. Am I right?

Originally posted by Synergy
What he means is that if his server1 goes down if that happens, then his site will show on server 2. Am I right?

Not exactly. I just wanted to know if I could create nameserver hosts ns3/ns4 from the same domain name and host them on another server. That's all.

Yes, that is possible.

Follow the documentations you used to install ns1 and ns2 on the first server, replacing ns1 with ns3 and ns2 with ns4 :D

Thanks, I feel more confident now :D

Originally posted by twrs
Thanks, I feel more confident now :D

All I can think is: Why?

_Why_ do you want a ns1 and ns2 on one server, and ns3 and ns4 on another server?

The normal solution would be to have ns1 on the first server, and ns2 on the second.

Originally posted by jks


All I can think is: Why?

_Why_ do you want a ns1 and ns2 on one server, and ns3 and ns4 on another server?

The normal solution would be to have ns1 on the first server, and ns2 on the second.


Yeah, if you had a more organized and specialized network. But for most virtual space providers its a different situation. Usually, if DNS is down, all sites pointed to are down too. So there is really no point in having two DNS server on different machines.

The only benifit I can see is that you can keep adding server without having to add new ns records. It will be also easier to move clients from one server to another. But then, for two server only, it might be easier to maintain each DNS server on its own machine instead of having a master/slave setup which can cause some confusion.

Originally posted by Ahmad



Yeah, if you had a more organized and specialized network. But for most virtual space providers its a different situation. Usually, if DNS is down, all sites pointed to are down too. So there is really no point in having two DNS server on different machines.


Okay, so you're basically saying that you should configure it wrong the first time, as you would probably first need it later? :-)

In addition, it wouldn't be rare to find customers who have (or wants) a backup MX for mail. If the DNS is down, their backup MX will perhaps not kick in. If DNS is working but the primary server is down, their mail will be stored on the backup MX.

Originally posted by jks


Okay, so you're basically saying that you should configure it wrong the first time, as you would probably first need it later? :-)

In addition, it wouldn't be rare to find customers who have (or wants) a backup MX for mail. If the DNS is down, their backup MX will perhaps not kick in. If DNS is working but the primary server is down, their mail will be stored on the backup MX.

You are right :)

So I will take my words back and say that I was just answering the question :D