I've runned a vps with hostname 'ns1.maindomain.com' and set dns entries of server which are asked in virtualmin configuration wizard to : ns1.maindomain.com , ns2.maindomain.com
Now, every alias domain I am adding to the server is getting its own name servers and soa records ! For example I add maindomain.net as alias, when I see its dns records, they seems as follow :
maindomain.net. IN NS ns1.maindomain.net. maindomain.net. IN NS ns2.maindomain.net.
Status:
Closed (fixed)
Comments
I've made a virtualserver with hostname domain (maindomain.com) and then trying to add alias to this cause each alias get its own nameservers and acts as a hostname which is wrong.
Submitted by andreychek on Fri, 08/26/2011 - 09:31 Comment #2
Howdy -- each Virtual Server (be it a top-level Virtual Server, a Sub-Server, or an Alias Server) would get it's own DNS zone file.
Each DNS zone should indeed have a set of NS records and a SOA... so that's all intentional :-)
Is there something different you were expecting to see?
The dns zone file is seperate in /var/named/ file and there is no problem here.
Why the Alias domains of hostname virtualserver are getting their own NS zons?? This is incorrect. Please see : I've set the default master NS records to ns1.maindomain.com and ns2.maindomain.com in virtualmin configuration wizard.
So I should set ns1.maindomain.com and ns2.maindomain.com for all my other domains which I want to use them on the server, This is OK I do it. For new virtual servers and alias of them the NS records are set to :
It's completely correct. BUT just create a virtual server with the domain of maindomain.com (which maindomain is your default hostname and so the default master NS domain), The try to create some alias on it, e.g. parkdomain-on-maindomain.com) You will see the alias domains will get these NS records :
But I've set the DNS entries of parkdomain-on-maindomain.com to ns1.maindomain.com and ns2.maindomain.com and the problem is here. The corret zones should be :
I've done my best to explain the bug I've founded in a clear way :)
Submitted by JamieCameron on Fri, 08/26/2011 - 10:40 Comment #4
Ok, I see the bug now .. this can happen if your master nameservers are in the same domain that is being aliased.
I will fix this in Virtualmin 3.88.
Submitted by Issues on Fri, 09/09/2011 - 11:23 Comment #5
Automatically closed -- issue fixed for 2 weeks with no activity.
This is very hurting and bothering bug ! Please release the new version asap.
Submitted by JamieCameron on Sun, 09/11/2011 - 10:49 Comment #7
It will be released this week.