I have 5 Virtuamin and webmin servers which do DNS duties one virtuamin PRO server which holds most of the domains - on the PRO server the other 4 servers are in two groups - one called NewDNS and one called OldDNS - there is also a group called ALL. the OldDNS group hold DNS secondarys linked to an old server which i am slowly migrating to the new Virtuamin PRO sever which has the NewDNS group as secondarys. So, i export a domain, import it to the PRO sever - it does its magic - i change the DNS pointers at the registrar and manually delete the secondary DNS from the OldDNS servers and i would think that would be it - BUT - when i check the migrated domain - it has the NS records for the Virtuamin PRO server which hosts it - the two secondary servers in the NewDNS group AND it also has NS records for servers in the OldDNS group... i do not think it should add ALL the servers that are "Webmin Servers Index" but only those servers listed in the "Cluster Slave Servers" menu of the Bind menu. - i deleted the extra name servers.
virtualmin pro creates extra nameservers.
Submitted by ashleydrees on Mon, 08/18/2014 - 16:59 Pro Licensee
Status:
Closed (fixed)
Comments
Submitted by JamieCameron on Mon, 08/18/2014 - 19:39 Comment #1
Yes, NS records should only be added for the primary and configured slave nameservers - not all registered Webmin servers.
If you add a new domain on the pro server, does the same thing happen?
Submitted by ashleydrees on Tue, 08/19/2014 - 01:37 Pro Licensee Comment #2
Ah... Yes. That is indeed the case. "Fresh" domains also have all registered Webmin/Virtualmin servers rather than the specified secondaries..
I,ll have to go through all the domains and delete the bad NS settings. I guess this is a bug then.
Submitted by ashleydrees on Tue, 08/19/2014 - 01:52 Pro Licensee Comment #3
That was boring.... But not why I am adding to the thread... I was using an ipad to delete the extra NS records... And on one domain, I touched the delete button twice - and Virtualmin deleted all the records... I am pretty sure that this is not the preferred behaviour. Once it had done that I was very careful not to press it twice again.
Submitted by ashleydrees on Tue, 08/19/2014 - 01:53 Pro Licensee Comment #4
Oh... One more thing... Domain alias are created correctly with just the NewDNS NS group...
Submitted by JamieCameron on Tue, 08/19/2014 - 12:19 Comment #5
Ok, it sounds like the correct behavior here is for Virtualmin to clear all existing NS records when restoring/migrating a domain, and then create only the correct local records.
Submitted by ashleydrees on Tue, 08/19/2014 - 12:41 Pro Licensee Comment #6
yes, that would be the best thing... plus not add all listed webmin servers to any fresh domain either.
Submitted by JamieCameron on Wed, 08/20/2014 - 23:49 Comment #7
Actually, I just checked the Virtualmin code, and it should already be removing existing NS records when restoring. Only NS records from the destination system should be included in the zone file, and should appear at the end.
Submitted by ashleydrees on Thu, 08/21/2014 - 01:23 Pro Licensee Comment #8
So, if the code is right, why is it adding all the managed servers - i do think it is removing existing and replacing... I guess I could add one more server that is not in the "new" group, and if that gets added there is more to work with (it will not appear anywhere in the old config setup). Actually, what can i do to help you with this?
Do you want to monitor the next migration... I have a couple more small ones before i do the major ones - or do you think either i am doing something dull or it is not a migration issue.
Submitted by JamieCameron on Thu, 08/21/2014 - 19:08 Comment #9
Would it be possible for you to attach a zone file to this bug report that contains the old correct nameserver records? I'd like to check their format and position in the file.
Submitted by ashleydrees on Sat, 08/23/2014 - 04:05 Pro Licensee Comment #10
Jamie. not completely sure what you need here.
You want a domain zone file from the Ensim CP server i am migrating from, which will have the pre migration NS records? NOT a file from the target Virtuamin Pro CP.
Submitted by JamieCameron on Sat, 08/23/2014 - 20:04 Comment #11
Oh, I see the issue now - I missed that you were migrating from Ensim, rather than from another Virtualmin system.
I see the issue now, and will fix it in the next Virtualmin release.
Submitted by Issues on Sat, 09/06/2014 - 20:11 Comment #12
Automatically closed -- issue fixed for 2 weeks with no activity.