DNS corrupt after backup restore

[Xandrios]

Hi,

I noticed that after restoring a backup my DNS became corrupt. Aswers like "SERVFAIL" would be returned. After a lot of searching I found out that the original zone has the following content:

domain.net. 100 IN A 69.77.xx.xx
ftp.domain.net. 100 IN CNAME domain.net.
www.domain.net. 100 IN CNAME domain.net.

While, after importing the backup, Directadmin adds the following:

www 100 IN A 69.77.xx.xx
ftp 100 IN A 69.77.xx.xx

Having both a CNAME and an A record does not work. And results in bind failing.

This happened while moving a backup from one server to another (IP change as well). After removing either the cnames or the A records (so that they are not duplicate & mixed) everything works fine again.

Is there a place to file bug reports?

 

[nobaloney]

I think this was discussed previously; perhaps a week to several weeks ago. There was a response from DirectAdmin Support explaining the issues and giving some suggestions.

Jeff

 

[Dravu]

Hi,

I noticed that after restoring a backup my DNS became corrupt. Aswers like "SERVFAIL" would be returned. After a lot of searching I found out that the original zone has the following content:

domain.net. 100 IN A 69.77.xx.xx
ftp.domain.net. 100 IN CNAME domain.net.
www.domain.net. 100 IN CNAME domain.net.

While, after importing the backup, Directadmin adds the following:

www 100 IN A 69.77.xx.xx
ftp 100 IN A 69.77.xx.xx

Having both a CNAME and an A record does not work. And results in bind failing.

This happened while moving a backup from one server to another (IP change as well). After removing either the cnames or the A records (so that they are not duplicate & mixed) everything works fine again.

Is there a place to file bug reports?

It looks like a fix will come in the next release:
http://www.directadmin.com/features.php?id=873

 

[Xandrios]

Ah, thanks! I did do a quick search but did not notice these. Good news, saves quite some zone-patching time