DNS Slave Auto-Conf. and remove server from Virtualmin's control

Hi, I made a mistake and removed the server from Virtualmin control. Then imported the Virtual Server. At this point, Virtualmin has created a duplicate entry in zone file for the slave dns server. (DNS Slave auto-configuration) After restarting the slave DNS server crashed.

Status: 
Closed (fixed)

Comments

I suppose this is rather a Webmin related problem on the slave server -- Webmin performs the zone synchronization on the slave side, initiated by Virtualmin on the master side.

Of course it should not create duplicate zone entries in any case. :)

If you haven't fixed the immediate problem yet: You might try editing the BIND config on the slave directly, using the Webmin BIND module, command "Edit Config File", then load the file that contains the zone references (named.conf.local in Ubuntu), look for the duplicate zone block and remove it.

After clicking "Apply Configuration" in the top-right corner, BIND should start up again.

Thanks, the problem is corrected. Supplement:

Master server:
Operating system Debian Linux 6.0
Webmin version    1.550
Virtualmin version 3.86.gpl GPL

slave:

Operating system Ubuntu Linux 8.04.4
Webmin version      1.550

That sounds like a bug ..

When you say you imported the domain, as this at Add Servers -> Import Virtual Server?

Yes, exactly!

1)I deleted the site (Disable and Delete -> Delete Virtual Server) ticking "Only remove server from Virtualmin's control, and leave website, users and databases untouched" 2)Add Servers -> Import Virtual Server 3)And got a problem (duplicate entries)

That is unusual, as the import process doesn't actually make any changes to the slave server ...

Did you do anything else after the import?

Also, was this zone inside a view on the slave?

I completely removed the site and made ​​them again. problem found in a few days after the operation. thought that during the import, I'm sorry for my mistake in the presentation of the situation.

Ok .. so do you have an idea of what action in Virtualmin might have triggered the extra slave domain creation? That would help us track down the cause..

I again tested the problem: 1) created a website. 2) removed the site. 3) there are no problems.

1) created a website. 2) derived from a control virtualmin. 3) imported in virtualmin. 4) delete the domain. 5) the problem! record in the zone file itself and a description of the zone remained. their files on the site! but the server does not return the zone.

Ok, I see the bug now .. slave DNS zones are not detected during the import process. I will fix that in Virtualmin 3.88.

Automatically closed -- issue fixed for 2 weeks with no activity.