SERVER_IP token wasn't present at dns_*.conf template parse time

Version 1.48

Bugfix
Finished

The |SERVER_IP| always worked before, but it was relying on the write-time parse of the named.db template. If you set webmail=|SERVER_IP| in the dns_a.conf, for example, it would have returned that text, without being swapped with the correct value. No real harm done, until you start playing with multi-IPs. If you add a 2nd IP, webmail=1.2.3.4 would have already been present, but because "1.2.3.4"!="|SERVER_IP|", DA allowed it to be added. Upon the named.db write, the |SERVER_IP| is tokenized, giving you duplicate A records for webmail, with the same IP. The fix is to make the SERVER_IP token available to all of the dns_*.conf templates, as they're tokenized.

Interested to try DirectAdmin? Get a 30-day Free Trial!