Admin level backup system

D

Djunity

Verified User
Joined
Mar 9, 2008
Messages
243
Location
Holland
Hi all,

We noticed that if you use the backup system to transfer accounts to other servers and off course select the shared server ip of the new server to use as ip address that when restoring the full dns zone gets reset to the default dns template as created by directadmin.

So for example we have an account with ip address 1.1.1.1 it uses an external mail server for example office 360 so mx record is diffrent.
On the new server the ip is 2.2.2.2 if you restore this account the mx record gets rewritten to 2.2.2.2 instead of keeping the mx record for office 360.

In my mind the backup system replaces the old server ip 1.1.1.1 in this case to the new 2.2.2.2 but it looks like the dns zone get rewritten compleetly to default, so my question is is this intentionaly or bug ?

In my opinion this sould not be intentionaly this way its hard to move over accounts if they have custom dnsd entry's
 
The last time I transferred all accounts on one server to another wich had different ip address, I did not get the problem you describe. That is not intentionally. Please contact DirectAdmin support to let them know about the problem/bug you experience.
 
its not only mx records also other adjusted A records where changed.
Its with 1.44 and older version on at least 2 servers that i know of.
 
Hello,

Hmm.. I wasn't able to duplicate that.

Here's a step-by-step to test my duplication attempt.

1) Created a new user called remotemx, with a domain remotemx.com, on the server IP 192.168.1.1.

2) Logged into to remotemx, and added an A record and custom MX record
Code: 
custommx  A  1.2.3.4
remotemx.com.  MX  custommx
where 1.2.3.4 will be our remote IP. I left the "mail" A record alone, and deleted the other mail MX record.

I also went to User Level -> MX records, and unchecked the "Local Mailserver" option.

3) Created a full backup at Admin Backup/Transfer

4) Deleted user remotemx.

5) Issued a restore of user remotemx, but select a shared IP 192.168.1.2 (just to confirm that it changed)

6) The result was the "mail" A record was set to 192.168.1.2, as it was swapped as expected.. and the custommx A record was still present, set to 1.2.3.4.
The only MX record present was to remotemx.com MX custommx.



Let me know if I'm missing anything, or if your steps are slightly different in case only certain combinations of steps work to get the error.

John
 
To clarify, you must be using an "A" record in the MX value part.
The MX record should point to an A record, and the A record to an IP.
An IP shouldn't be in the MX record.

John
 
You must log in or register to reply here.
Back
Top