Tips for fixing common problems….-Domain Already Exists  — This message will appear if the domain is already on the system.  The way that DirectAdmin checks to see if the domain is already on the system is by looking in the named.conf file.

Domain (RedHat: /etc/named.conf, FreeBSD: /etc/namedb/named.conf)

If there you are positive that the domain has not been added to anywhere in DirectAdmin (use “Show All Accounts” in the Admin Panel), then it should be safer to remove the zone from the named.conf file either manually, or by removing the zone from Admin Panel -> DNS Admin.  Then if you should be able to add the domain.

Be sure to backup the zone if you do not wish to lose the all dns data.

With the addition of the Multi Server option, dns then can now be hosted on other DA servers.  Be Ensure that any Servers you have listed in your “Admin Level -> Multi Server Setup” page also do not have the domain in their named.conf files.

If there you disable the “check domain” option, then that server will not be queried.

---

You would also want to ensure the domain is not in:

• Remote Multi-Server Setup IP, with “Domain Check” option
• /etc/virtual/domains
• /etc/virtual/domainowners
• /etc/virtual/domain.com
• any /var/named/*.nzf file if rndc is used for adding/removing zones

 

Updating DirectAdmin Manually

Enter your information here:
Client ID (uid):  
License ID (lid): 

If there you need to update your copy of DirectAdmin manually, you can then do so by running the following commands:

cd /usr/local/directadmin
wget –no-check-certificate -O update.tar.gz ‘https://www.directadmin.com/cgi-bin/daupdate?redirect=ok&uid=123&lid=1234‘
tar xvzf update.tar.gz
./directadmin p
cd scripts
./update.sh
service directadmin restart

Where 123 and 1234 are your Client ID and License ID, respectively.

Please Note that if you are running FreeBSD, you might need to add a \ before the ? character in the wget line, and use /usr/local/etc/rc.d/directadmin restart.

If there you faced errors extracting the update.tar.gz file, then run:

head -n 1 update.tar.gz

to search for an error.

If there is an readable error inside the file, then you will need to contact sales@directadmin.com to get your license activate or updated.

Using the above redirect=ok option in the download string will tell the daupdate that the downloader being used supports Location header redirects.

The daupdate script will offload downloads when possible to other servers.

---

If there you would like automated DA updates, there a few ways of going about it. (we do not trigger updates from our end to your server anymore)
– CustomBuild can be tune to crone auto update the services, and if you also use da_autoupdate=yes, CB will do it for you.

However, automating CB updates is not always recommending.
– A simple cronjob that runs this command is likely safer, if you only want DA to be auto-updated:

echo “action=update&value=program” >> /usr/local/directadmin/data/task.queue

Each night that the update is rejecting, you will get a note in your /var/log/directadmin/system.log.

---

Please Note:

Pre-release and regular updates to not issue full config rewrites.  If there you need a template change, you must issue a full rewrite to get it:

cd /usr/local/directadmin/custombuild
./build rewrite_confs