Reseller Step-by-Step Guide
3 - DNS Zone propagation
Step 1: Creating Name servers
Once you have created your name servers in the Control Panel, you will have been assigned unique IP addresses for each of them
In order for your name servers and DNS zone to work, you must create these name servers with the Domain Registrar you have registered your dns zone domain with. Most domain registrars provide some provision to allow you to create your own name servers with them. Please contact them or read their Help guides to find out how.
If you registered your DNS zone domain with us as your registrar (from http://www.hostdepartment.com/dnr - this is recommended), click on "Register Name servers" for your domain to create the name servers in the member area of your DNR account. Or you can also contact our DNR support at email@example.com for assistance in this regards.
In the case above (if mycompany.net was your DNS host name), you'd have to create all the listed name servers for mycompany.net at your domain registrar, pointing to each of their corresponding IPs. i.e.
ns2.mycompany.net --> 18.104.22.168
ns1.mycompany.net --> 22.214.171.124
Note: (your actual IPs may vary)
Once you have created the name servers at your domain registrar, you must then point your DNS Zone domain to its authoratative DNS servers so your server aliases (such as cp.mycompany.net) would work. Once you complete these steps for your DNS zone host name, you'd have to wait 24 to 72 hours for DNS zone propagation to complete.
Step 2: Verifying your DNS zone
Once you have waited 24 to 72 hours for your DNS zone to propagate, you'll have to verify that you can "ping" your name servers as well as server aliases. If your DNS host name were mycompany.net, try pinging cp.mycompany.net to see if your DNS zone has propgated correctly. If you have not yet waited for 24 to 72 hours, please skip this step and the next step and come back here once you have waited for 24 to 72 hours.
In Windows, Click on the "Start" Button and then click Run and type in "cmd" in the box. Click the OK button.
Then type in "ping cp.mycompany.net" (where mycompany.net is replaced with YOUR DNS host name) in the C:\ Command prompt. If you see a screen like below where cp.mycompany.net is resolving into an IP, your DNS zone has propagated properly:
If you do not see a screen like this and instead, the Window closes immediately or you get "Host cannot be found", then your DNS zone hasn't propagated correctly and you may contact firstname.lastname@example.org
You can also use this method to ping and check your name servers and other server aliases (tulsa.mycompany.net, watson.mycompany.net, mail.mycompany.net, etc.) If anyone of them doesn't resolve into an IP, you may contact email@example.com
Step 3: Changing your Control Panel's URL
After DNS zone propogation has been completed and you can ping cp.mycompany.net (where mycompany.net is replaced by your DNS host name), you must follow these steps to make your control panel actually work. If your DNS zone has not propagated yet (if you have not waited for 24 to 72 hours), please skip this step and move to the next. You can come back to this step when propagation is complete.
Login to your reseller account like before from the CP url sent to you in your Welcome email:
After logging in, you should see a screen like this:
From the "Info" dropdown menu, select "Change URL".
1) Protocol is http:// and NOT https:// (Use HTTPS only when CP SSL is enabled - refer to Reseller Documentation).
2) Given control panel url is cp.mycompany.net (where mycompany.net is replaced by your DNS host name).
3) Port is 80 or leave it blank and NOT 443. (Use 443 only when CP SSL is enabled).
Once done, click "Change". You'll be taken back to the same screen.
Now you can access your control panel from http://cp.mycompany.net (where mycompany.net is replaced your DNS host name). You can now directly use http://cp.mycompany.net to login into your Administrative Account. Just enter the username and password you entered while creating the Administrative Account.