DA does not appear to be picking up the dns_a.conf custom template correctly.

netmotiv8

Verified User
Joined
Sep 26, 2003
Messages
204
Location
UK
DA does not appear to be picking up the dns_a.conf custom template correctly.

Some urgent help needed here!

Our custom file is here:

-rw-r--r-- 1 diradmin diradmin 123 Apr 4 15:32 /usr/local/directadmin/data/templates/custom/dns_a.conf


but DA is using:

-rw-r--r-- 1 diradmin diradmin 67 Jun 14 18:46 /usr/local/directadmin/data/templates/dns_a.conf

the custom template works fine on new domains & when manually adding a dns record, however when 'moving' a user from a shared IP to a owned IP the custom template is not used correctly.

DA seems to be using the custom template but putting its own ips in.


Is this a bug?



Neil :D
 
Hello,

When changng the IP of a User, the ip's are swapped directly from the zone.. word for word. No templates are used.

John
 
But then this is not correct. Here is our problem:

Please note, the ip address quoted are for example purposes and not what we are actually using:

The standard dns_a.conf template looks like this:-

|DOMAIN|.=|IP|
localhost=|IP|
mail=|IP|
pop=|IP|
www=|IP|
ftp=|IP|

The custom template we have made looks like this...

|DOMAIN|.=|IP|
localhost=|IP|
mail=192.168.0.116
pop=192.168.0.116
www=|IP|
ftp=|IP|
imap=192.168.0.116
smtp=192.168.0.116

Once we moved the user, the actual zone file had all ips as 192.168.0.117 rather than a mixture of 192.168.0.116 & 192.168.0.117 as we believe it shoud have had.


The reason we need it done like this is to enable us to just run the mail software on 1 ip.... as we dont see the point or wish having stuff listening on all ips.

We did find that upon deleting & readding the zone the situation was fixed.

I look forward to your comments.



Neil :D
 
Hello,

DA assumes that if you are changing the IP of a zone from one to another, all old IPs should become the new IPs. This should be the case when a user has added subdomains to his dns record. They won't be in the templates, but they must be changed as well.

Since the templates are not used for IP changing, you'll have to continue with the same method of removing/adding zones to get the desired effect that you are looking for. New domains should correctly use your custom records.

John
 
Back
Top