External DNS server on VPS as a primary DA dns server.

Richard G

Verified User
Joined
Jul 6, 2008
Messages
14,148
Location
Maastricht
My friend has a DA server in Germany with 1 ip and a VPS in the Netherlands with 1 ip (he maybe can get a second ip here if needed).
He definately wants to run his own authoritive nameservers but he can't get a second ip.

So I thought that we could use the VPS also as slave server (2nd namserver) for the DA server.

I have been looking for a howto, but either it's too complicated for me (too much info and things to think about I problebly don't need), or the information is too old.
In the Howto section here on the forum there is also a bit of an explanation, but that post is from 2004 which is 8 years old.

The VPS does not need to be used as a primary nameserver, it runs some apps and a webserver.
But concerning the DNS purposes it only needs to function as secondary nameserver (slave server) for the German DA server.

Is there an easy way to set this up and make this function? With as little scripts as possible, because I don't know anything about scripting, I'm good with copy and pasting though.:D

German DA server is Centos 6 64-bit with Bind 9.8.2-0.10.
VPS is a Centos 5 32-bit server with Bind 9.3.6.

It would be nice if the slave server (secondary dns on the vps) would be updated every time a change is made in some domains DNS on the DA server.
Is this possible with the 1 ip on the VPS or do we still need a second ip on the vps?
 
I had found the first one before, but that is also from 2005, which I find too old.

The second link can be of great help probably.

Thank you!
 
Master2Slave DNS replicator is from 2005, but it's still quite usable; I still use it on all new servers. However not all required changes (for security) are well documented.

Jeff
 
Thank you Jeff, but since I'm not very good in scripting and slave dns, I really need something well documented to be sure that I don't do anything wrong.
That's why I'm going to try "Directslave" first.
 
No problem; for most people it's probably easier to implement. I continue to use Master2Slave DNS Replicator because it's universal; it doesn't require DirectAdmin for either master or slave.

Jeff
 
Well... I still might think about using Master2Save due to errors with Directslave.

However I got another problem now. Bind is running on my VPS, but when I do a DNS check, the server is not seen.
I will make another topic for this.
 
I bumped this thread because I have a question.
Master2slave is running fine now with the vps second ip as secondary nameserver.

Now I have the following question. Is it possible the use this ip and Master2slave on this VPS for multiple servers? So we use this as secondary dns server for other servers too?
 
Master2Slave DNS Replicator can be set up for any reasonable combination of masters and slaves; complete information should be in the ReadMe file.

Jeff
 
Yep, I know that Jeff... but my question was if one could use multiple secondary DNS servers (using master2slave) on 1 ip address. So I mend the more 2nd dns servers on 1 ip.
 
You can set as many nameserver names as you wish, pointing one IP#. Neither Master2Slave DNS Replicator nor BIND cares. Your TLD's registrar may (some TLDs do). But you're not getting any advantage in doing so.

ns1.example.com and ns2.example.com should always point to different IP#s on different servers, preferably on different networks, as ours do, for real redundancy.

Jeff
 
I know they should point to different ip's for real redundancy.

But I ment using the 1 ip of a VPS for several secondary nameservers like this.

VPS with 1 ip being:
ns2.example.com and ns2.otherdomain.com and ns2.somedomain.com

The ns1's for those domains are all on different servers where those domains are residing and they ofcourse have different ip's and different locations.

Reading your answer, I understand that this way it's no problem at all and also a good way to keep real redundancy without disadvantages.
I just was not sure if it was possible and a good way of working to put multiple (but different) ns2 servers on 1 ip address.
 
No problem with Master2Slave DNS Replicator or with BIND on doing this, but no matter what you call your nameserver, when it replies back the reply will come back with the name as pointed to by the rDNS on the main server IP#.

Jeff
 
Back
Top