Quote Originally Posted by RodG View Post
Why? You really aren't leaving any room for error.



In this instance there shouldn't be any delay whatsoever. You have defined a brand new host - there isn't going to be any 'stale' data for it anywhere that would cause any delays. HOWEVER, *if* you happen to make a mistake it is now going to take up to 12 hours before it can be fully rectified.

As for the SSL - you can very easily run into trouble here because a certificate for 'mydomain.com' will NOT be valid for 'sub.mydomain.com' (just as it won't be valid for 'www.mydomain.com').

Furthermore, the setting
define('HTTPS_SERVER', 'https://your account IP/~my-cpanel-account-name/sub'); // ssl url

... is generally considered very "unprofessional" and there are only a couple of rare instances where this format would actually be needed - Typically 1) where it is a completely new domain and you wish to work ion the site before it will resolve, and 2) Where you are using a host supplied shared SSL - in which case the 'your account IP' will be your hosts shared server name - followed by the ~my-cpanel-account-name/sub.

If I thought that SSL offered anything more than 'warm fuzzies' and a false sense of security, I would actually avoid a site that presented me with a URL of the type that you have defined. :-)

Apologies for the apparent criticism, your method has obviously worked for you, so one could make a valid argument that there is little or nothing inherently *wrong* with this approach - but IMO it isn't the best approach. If I/we ignore the SSL aspect, you really haven't left any room for possible errors when making the DNS additions/changes - and that is the biggest 'issue' I have here.

I guess it could just be me that occasionally gets things wrong in this regard (dyslexia) - but I hate to admit how many hours I would have wasted over the years "chasing shadows" and waiting for DNS updates before I've been able to move forward. The advanced planning and reducing the TTL's to the absolute minimums allowed by the ISP really has saved me a lot of time, frustration and self annoyance at being so 'stupid' for messing up in the 1st place. ;-)

Ergo, I put this message to you NOT as a criticism as to what you have done, but as a little bit of friendly advice (personal experience) as to how you could possibly save yourself a few headaches in the future (should you ever need to go this path again).

As I stated previously, the reduction in the TTL's is best considered as a form of 'insurance'. It's not essential, but its a bleeding nice thing to have for when things don't go as planned.

Cheers
RodG
Hi RodG,

I appreciate your feedback and observation! All valid points...However, I think you missed the purpose of my original post. This was for TESTING PURPOSES only using a subdomain on a different server.

...I would like to install and test the new Zen Cart on server B, including email and SSL before switching it live...
So, yes, if one were going live with this setup...not the preferred method. That's why I included the link from mc12345678 in my last reply. The link is to the preferred method once testing is done and you want to set your new site live!

Thanks again for all of your input! Got it all worked out!