3 - DNS Zone propagationStep 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 the case above (if mywebhost.net was your DNS host name), you'd have to create all the listed name servers for mywebhost.net at your domain registrar, pointing to each of their corresponding IPs. i.e. ns4.mywebhost.net > 204.10.105.200 ns3.mywebhost.net > 204.14.104.150 ns2.mywebhost.net > 204.14.106.14 ns.mywebhost.net > 204.14.104.105 (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.mywebhost.net) would work. If you are performing this setup after August 6, 2005, your authoritative DNS servers would be ns3 and ns4. Hence you'd need to set the name servers of mywebhost.net at your registrar to: ns4.mywebhost.net (204.10.105.200) ns3.mywebhost.net (204.14.104.150) If you created your DNS Zone before or on August 6, 2005, your authoritative DNS servers would be ns and ns2. Hence you'd need to set the name servers of mywebhost.net at your registrar to: ns2.mywebhost.net (204.14.106.14) ns.mywebhost.net (204.14.104.105) Once you complete these steps for your DNS zone host name, you'd have to wait upto 72 hours for DNS zone propagation to complete . Step 2: Verifying your DNS zone Once you have waited 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 mywebhost.net, try pinging cp.mywebhost.net to see if your DNS zone has propgated correctly. If you have not yet waited 72 hours, please skip this step and the next step and come back here once you have waited 72 hours. In Windows, Click on the "Start" Button and then click Run. Type in cp.mywebhost.net (where mywebhost.net is replaced with YOUR DNS host name)
You can also use this method to ping and check your name servers and other server aliases (win9.mywebhost.net, win10.mywebhost.net, mail.mywebhost.net, etc.) If anyone of them doesn't resolve into an IP, contact [email protected] Step 3: Changing your Control Panel's URL. After DNS zone propogation has been completed and you can ping cp.mywebhost.net (where mywebhost.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 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:
1) Protocol is http:// and NOT https:// (Use HTTPS only when CP SSL is enabled - refer to Support Manual) 2) Given control panel url is cp.mywebhost.net (where mywebhost.net is replaced by your DNS host name) 3) Port is 80 and NOT 443. Use 443 with CP SSL
Now you can access your control panel from http://cp.mywebhost.net (where mywebhost.net is replaced your DNS host name). You can now directly use http://cp.mywebhost.net to login into your Administrative Account. Just enter the username and password you entered while creating the Administrative Account. |
Next >> |