Problem restoring alias domain

Submitted by LonDoh on Tue, 11/20/2012 - 09:43

I have a problem restoring an alias domain

The main domain restores OK and works fine (when viewed thru VM preview) But the alias domain fails with this error

     Re-creating records in DNS domain ..
    .. domain not found!

.. failed! See the progress output above for the reason why

And so the dns zone for the alias domain hasnt been created there are no obvious errors from bind when restore fails

These are backups from an old box being restored onto a new one. the zone files on the old box look good I've redone the backups, but still same error. Other similar main/alias backups have restored OK

Any ideas please?

Status: 
Active

Comments

Submitted by Locutus on Tue, 11/20/2012 - 09:51

I suppose the error message is from the Restore step. Before the actual restore, the domain should get created if it didn't exist before. Can you see a message during the Create step that confirms that the DNS feature was turned on and a zone created?

Make sure that under "Other restore options" the setting "Only create servers with selected features" is turned off, so that the original features of the domain being restored are turned on.

Submitted by andreychek on Tue, 11/20/2012 - 10:02

Yeah, verifying that the DNS feature is enabled for the primary domain is a good first step.

If for some reason that weren't enabled, that could cause the problems you're seeing.

Submitted by LonDoh on Tue, 11/20/2012 - 10:33

Yes as I said: "The main domain restores OK and works fine" I have now re-tried this as 'with sub servers' selected in the backup config. And also as individual domains backup/restore

the nameservers havent been switched yet, but 'dig example.com' on the new box returns correct info The domain details are correct in webmin Bind module, and the zone file is in the right place and on inspection looks perfect.

Everything works fine on the old box. Same tests show all OK. There's a 301 redirect in place that works ok.

I dunno - which is why I asked, but life is too short and Its quicker if I just recreate the alias and email users. Almost all others so far are OK just this one with this problem. I have another 300+ plus to go. Leave it for now and I'll be back if any more probs.

[btw: this editor doesnt always do what it says it will with 'carriage returns']

Submitted by Locutus on Tue, 11/20/2012 - 11:22

You're mixing up "main domain" with "creation step". :)

The restoration process not only of the main domain, but also of your alias domain, consists of two steps: First, the alias domain is created, just as if you'd have done that manually. (Alias domains can have the DNS feature turned on or off, independently from the parent.) Then, the contents of the backup are extracted and put into the newly created domain.

If the first step fails to set up the DNS feature correctly, putting the backup data into it cannot work.

That's why Eric and me were basically asking for a transcript of the whole restoration process. From that we can see if the DNS feature was set up correctly.

Submitted by LonDoh on Wed, 11/21/2012 - 10:59

For the record I hit this problem again a couple times.but I didnt see a pattern to it.

You're mixing up "main domain" with "creation step". :)

then you'd best define "main domain" and "creation step" for me please

That's why Eric and me were basically asking for a transcript of the whole restoration process

you probably also need to define "transcript of the whole restoration process" too!

And perhaps I missed where you asked for that?

Anyway, I followed same procedure as I wrote above and as outlined in this page: https://www.virtualmin.com/documentation/system/backup-and-restore

particularly these points:

1) Create a backup on the source system containg the top-level server you want to transfer, and all sub-servers. The Include sub-servers checkbox on the backup form makes this easy.

3) Use the restore form to re-create the domains from the backup files. If you select them all at once, any top-level servers will be restored before sub-servers, and their heirarchy correctly preserved.

I put some faith and expectation in 1) "Include sub-servers checkbox on the backup form makes this easy" and 3) with the mention of "hierarchy preservation".

But as I explained I also tried to backup/restore them as individual domains. The failure error was the same in those domains which would not restore.

Anyway its mostly done and I've worked around it by just re-creating rather than restoring the offending alias domains.

thanks very much for your input

Submitted by Locutus on Wed, 11/21/2012 - 12:08

My apologies, I wasn't aware that the terms used in my post were so unclear.

then you'd best define "main domain" and "creation step" for me please

You yourself used the term "main domain", as opposed to "alias domain". I was assuming that with "Main domain" you meant the one that the "alias domain" is an alias of.

"Creation step" I outlined in my previous post, second paragraph, starting with "...the restoration process...consists of two steps".

you probably also need to define "transcript of the whole restoration process" too!

You quoted two lines from the restoration process, showing the error. We'd need to see ALL the lines that Virtualmin prints during the restoration process. Especially those from the DNS creation step.

And perhaps I missed where you asked for that?

In the following line in my first post I indirectly asked for it:

"Can you see a message during the Create step that confirms that the DNS feature was turned on and a zone created?"

Submitted by LonDoh on Wed, 11/21/2012 - 13:26

Anyway its mostly done and I've worked around it

thanks again