DNS - Chicken or egg?

4 posts / 0 new
Last post
#1 Tue, 12/29/2009 - 13:20
pablofm

DNS - Chicken or egg?

Hi there,

I have a question that I am having a hard time answering. Let me describe:

I have a domain: domain.com

I want to use this domain for everything I am going to do with cloudmin, virtualmin, webmin.

I want to setup cloudmin to use the domain.com as the basis for the install. So, I install cloudmin on a server and go into webmin an immediately setup a zone for domain.com. I created name servers also dns1.domain.com and dns2.domain.com using 2 IP address from the master server.

I also setup so that all new xen nodes are named *.xen.domain.com

So, my new virtualmin xen server is called: virtualmin.xen.domain.com.

This works great and DNS is operating correctly with the zones correctly updated when I add/remove a xen instance, etc.

Now, here's my question:

I want to install Virtualmin on the virtualmin.xen.domain.com xen instance. I want Virtualmin to manage the same DNS servers (dns1.domain.com and dns2.domain.com). Do I cluster the virtualmin.xen.domin.com DNS servers with the master DNS server? Is that what I need to do?

Is there a giude (or can someone please reply with a howto) on how to do this? I am sure it's simple, but my brain is going into an endless loop as I think about this one.

I should also add, that I will want to create a Virtual Server called domain.com where I will host the public web site for the service. If I do this, will it clobber the domain.com zone? I hope this makes sense.

Any help is greatly appreciated.

Thank you!

Tue, 12/29/2009 - 14:43
JamieCameron

To make things simpler, you could just fully host DNS for any domains on the virtualmin.xen.domain.com system on the system itself. When registering those domains, just use its IP as the nameserver.

Alternately, you could setup dns1 and dns2 as slave servers for a master on virtualmin.xen.domain.com , and use the IPs of dns1 and dns2 when registering domains.

As for the domain.com website, I would recommend keeping its DNS hosted where it is now, and just point the A record for www to the virtualmin.xen system. Then on that system create a regular virtual server for domain.com , but without the DNS feature enabled.

''

Tue, 12/29/2009 - 15:03 (Reply to #2)
pablofm

Hi Jamie, thanks for the reply.

To make things simpler, you could just fully host DNS for any domains on the virtualmin.xen.domain.com system on the system itself. When registering those domains, just use its IP as the nameserver.

OK, so I understand correctly: you suggest I leave the cloudmin DNS where it is (on the master server). But, from now on use the virtualmin.xen.domain.com DNS server to manage DNS globally. OK, but do I need establish a master/slave relationship between the master and the virtualmin DNS's ?

I am not sure I follow this correctly. Here's what I understand: In order to setup cloudmin to begin with, you need DNS. So if DNS is installed after I setup cloudmin on the master AND cloudmin modifies the zone every time I create a new instance (i.e. adding instanceX.xen.domain.com to the domain.com zone record) this means that DNS needs to be running on the master for cloudmin to work properly.

Alternately, you could setup dns1 and dns2 as slave servers for a master on virtualmin.xen.domain.com , and use the IPs of dns1 and dns2 when registering domains.

OK, so the virtualmin DNS server becomes the master DNS server. I would then change the current cloudmin master DNS server to behave as a slave. I suppose slaves update servers when changes are made, so domain.com would be updated globally when the cloudmin master made any new *.xen.domain.com zone records. How do I make the cloudmin master DNS into a slave of the virtualmin.xen.domain.com DNS server?

As for the domain.com website, I would recommend keeping its DNS hosted where it is now, and just point the A record for www to the virtualmin.xen system. Then on that system create a regular virtual server for domain.com , but without the DNS feature enabled.

Just to be clear, right now the DNS is hosting on the cloudmin master DNS server using webmin. So, leave it here for now and use option #1 (i.e. use virtualmin to manage global DNS)?

Sorry for all the questions, I am trying to map this out step-by-step and really appreciate your help!

Thanks

Wed, 12/30/2009 - 00:21 (Reply to #3)
JamieCameron

If you are setting up Cloudmin from scratch, it generally assumes that you already have a DNS domain setup somewhere - call it domain.com for example. This could be hosted on the Cloudmin master system or elsewhere.

You can then create a sub-domain like xen.domain.com on the Cloudmin master, and add NS records to the domain.com zone pointing to the Cloudmin master .. that way new entries under xen.domain.com will be resolvable from outside.

New Xen instances will get hostnames and DNS entries like foo.xen.domain.com. If one of these runs Virtualmin, it can also host DNS for the domains you create using Virtualmin. For additional redundancy, you could setup the Cloudmin master as a slave of the Virtualmin instances, so you have two nameserver IPs to give to the registrar.

''

Topic locked