How to Create Users in DirectAdmin Reseller & Update Domain Nameservers

Follow these steps to create a new user account under your reseller package:

• Log into DirectAdmin using your reseller login credentials.
• Ensure you are at the Reseller Level interface (switch level at the top right if necessary).
• Navigate to Account Manager and click Add New User (or Create User).
• Fill in the user creation form:
  
  • Username: Enter a unique username for your client's account.
  • Email: Enter the client's email address.
  • Password: Enter or generate a secure password.
  • Domain: Enter the user's primary domain name (e.g., example.co.ke).
  • Package: Select a pre-configured hosting package or assign resources manually.
  • IP Address: Select the designated IP address for the user (usually the shared reseller IP).
• Click Submit or Create Account.
• Once created, DirectAdmin generates the zone files and sends login credentials to the client's email.

If HOSTAFRICA is the domain registrar, update the nameservers in the Client Area to point the domain to your DirectAdmin server or reseller.

Important: DirectAdmin hosting uses different nameservers than cPanel hosting.

Ensure you assign the correct DirectAdmin nameservers:

• Primary Nameserver: dan1.host-ww.net
• Secondary Nameserver: dan2.host-ww.net

• Log into the HOSTAFRICA Client Panel.
• From the main menu, navigate to
  Domains > My Domains.
• Locate the domain name you wish to configure and click Manage (or click the wrench icon).
• Select Manage Nameservers from the sidebar menu.
• Choose Use custom nameservers (enter below).
• Replace any existing nameservers with:
  
  • Nameserver 1: dan1.host-ww.net
  • Nameserver 2: dan2.host-ww.net
• Click Change Nameservers to save.

• DNS Propagation:
  DNS changes take 2 to 24 hours to propagate globally across all networks.
• Order of Execution:
  Always create the user account inside DirectAdmin before or immediately after updating nameservers. If the domain is queried before the zone file exists on the server, it will return a "Site Cannot Be Reached" or missing NS record error.
• Parent Server Glue Warnings:
  Diagnostics reporting NO GLUE for dan1.host-ww.net or dan2.host-ww.net are normal standard responses for external root servers and do not indicate a failure.