Submitted by miner on Sat, 08/08/2009 - 17:34
I was copying domains to a second server which was already serving DNS, so I deselected DNS from the restore options.
The restoration failed because of pre-existing DNS (in named.conf.local)
So I removed the zones from named.conf.local and still deselected DNS from the restoration options.
The restoration created DNS anyway, even though it was deselected.
Maybe it thinks it has to, so you can kill this report. I would have done better to have not included it in the export/backup, or to have removed the DNS from Virtualmin control before export/backup.
Status:
Closed (fixed)
Comments
Submitted by JamieCameron on Sat, 08/08/2009 - 21:29 Comment #1
Yes, this is expected .. even if you don't restore the DNS, when creating a domain from a backup DNS will still be created. The only way to prevent this is to select "Only create servers with selected features?" on the restore form as well.
But in general, you don't want this kind of clash to happen in the first place - removing the DNS domain from named.conf.local is the right thing to do.
Submitted by Issues on Sun, 08/23/2009 - 04:18 Comment #2
Automatically closed -- issue fixed for 2 weeks with no activity.