I spend most of my time on stack overflow, so I hope I have the right site.
As long as I can remember I have always ran a small ispconfig cluster,
myispconfighost.com. During this time I have used a separate domain dedicated to dns. So I had:
www.cluster1.com ns1.generic-dns-domain.com ns2.generic-dns-domain.com
I am in the process to starting a cPanel farm as an alternative control panel. As some people like the reputation of the name.
Anyway. My question. Should a host use the same name server domain? Best explained by example..
Separate dns domain:
cluster1.com ns1.cluster1.com ns2.cluster1.com cluster2.com ns1.cluster2.com ns2.cluster2.com
Combined dns domain:
cluster1.com cluster2.com ns1.generic-dns-domain.com // cluster1.com dns server 1 ns2.generic-dns-domain.com // cluster1.com dns server 2 ns3.generic-dns-domain.com // cluster2.com dns server 1 ns4.generic-dns-domain.com // cluster2.com dns server 2
Each of the above are separate servers with their own IP. But is there a preferred way to name your nameservers when you require more than one group of name servers?
I realise I should explain the reasoning for those not familiar with the automation of the control panels.
Ispconfig will create / update zone files. cPanel will create / update zone files.
Neither (by default) talk to each other. So if you used one server (ns1) and installed cpanel and ispconfig, the only data you would have is the last one to update the server, since cpanel and ispconfig will have different dns zone information.