How to Configure Private Nameservers for Reseller Hosting
Private nameservers allow you to use your own domain name for DNS instead of showing the default hosting provider nameservers. This is useful for resellers who want to provide a more professional and branded hosting service to their customers.
For example, instead of using provider nameservers, you can use:
ns1.yourdomain.com
ns2.yourdomain.comFollow the steps below to configure private nameservers for your ApnCloud Reseller Hosting service.
1. Check Your Reseller Hosting Details
Before creating private nameservers, make sure you have the correct server information for your Reseller Hosting account.
You may need:
- Server IP address
- Primary nameserver details
- Secondary nameserver details
- Your reseller domain name
Use the server information provided with your ApnCloud Reseller Hosting service.
2. Choose Your Private Nameservers
Select the nameservers you want to use with your domain.
Common examples are:
ns1.yourdomain.com
ns2.yourdomain.comReplace yourdomain.com with your actual reseller domain.
3. Create Child Nameservers at Your Domain Registrar
Log in to the domain registrar where your reseller domain is registered.
Look for an option such as:
- Register Nameserver
- Child Nameservers
- Glue Records
- Host Records
- Private Nameservers
The exact wording depends on your domain registrar.
4. Register ns1 and ns2
Create the first private nameserver:
ns1.yourdomain.comAssign it to the appropriate server IP address.
Then create the second private nameserver:
ns2.yourdomain.comAssign it to the appropriate server IP address provided for your hosting setup.
5. Configure Nameservers in DirectAdmin
Log in to your DirectAdmin Reseller Panel.
Look for the nameserver or reseller settings section and configure your private nameservers if the option is available.
Enter your preferred nameservers, such as:
ns1.yourdomain.com
ns2.yourdomain.comSave the changes after reviewing the information carefully.
6. Check the DNS Records
Make sure the required DNS records for the private nameservers exist and point to the correct server IP addresses.
For example:
ns1.yourdomain.com → SERVER_IP
ns2.yourdomain.com → SERVER_IPThe exact DNS configuration depends on your hosting and network setup.
7. Update Customer Domains
After your private nameservers are configured, you can ask customers to use them for domains hosted under your reseller account.
For example:
ns1.yourdomain.com
ns2.yourdomain.comCustomers can enter these nameservers at their domain registrar.
8. Wait for DNS Propagation
Nameserver and DNS changes may not become active immediately.
DNS propagation can take some time depending on the registrar, DNS provider, previous DNS cache, and network conditions.
During propagation, some users may still see the old server or DNS information.
9. Test Your Private Nameservers
After propagation, confirm that your private nameservers are resolving correctly.
Check that:
- ns1 resolves to the correct IP address
- ns2 resolves to the correct IP address
- Customer domains resolve correctly
- Hosted websites load from the correct server
- DNS records are working as expected
Common Problems
If your private nameservers are not working, check the following:
- The child nameservers were registered correctly
- The correct server IP addresses were used
- The required DNS records exist
- The domain uses the correct nameservers
- DNS propagation has completed
- There are no typing errors in the nameserver names
Important Tips
- Use the exact server IP information provided for your reseller service
- Do not change nameserver records randomly
- Keep your DNS configuration consistent
- Allow enough time for DNS propagation
- Test customer domains after making changes
Need Help?
If you are unable to configure your private nameservers or the nameservers are not resolving correctly, please open a Support Ticket from your ApnCloud Client Area.
Include your reseller domain, private nameserver names, and a clear description of the issue. Never include passwords or sensitive login credentials in the ticket.
