Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Recently there is a fault in DirectAdmin's underlying scripts that after a user is created with respective domains, DA failes to reload the Apache service for the new configuration to take effect which leads to the 404 error upon calling the said domain.

I wonder what could be the problem and how could it be fixed?

share|improve this question

closed as off-topic by HopelessN00b Apr 9 '15 at 14:28

  • This question does not appear to be about server, networking, or related infrastructure administration within the scope defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.

up vote 2 down vote accepted

Well, I'm not sure where the problem might be, but rebooting the server doesn't seem to be a wise choice. Try first to reload (or restart) the named service:

service named restart

By doing that you can be sure that it's a DNS-related issue. Then you should look into /var/log/messages to search for errors on named service or other issues. Also, you might want to check Directadmin's log files: /var/log/directadmin/error.log and /var/log/directadmin/errortaskd.log

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.