This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
May 22, 2008 11:08pm
Subscribe [4]#16 / Jun 11, 2008 11:48am
I’ll contact the current host and have them add that DNS Zone setting (I think they’re on IIS and I may have to wait HOURS for it to get done. Small Town web host “service” at its best…) but I will definitely contact you if I can’t get it working. And of course, I’ll post back here if I get it working so I can use this thread as future reference.
Thanks for your support, slapshotw!
#17 / Jun 11, 2008 11:55am
You may even want to consider making the account on the new server just “domain.com,” and parking “dev.domain.com” on it, because it’ll mean you don’t have to move files around when you want to launch. You’ll just need to change the IP/nameservers of domain.com to point to the new server. That’s taking it to another level though 😊.
#18 / Jun 11, 2008 12:10pm
Sweet! Not wanting to wait for Small Town Host to go in and make changes I decided to test this. I went into WHM for masugadesign.com and added “redwings” like so:
redwings 14400 IN A 00.000.00.000Then I went to the new server and added an account for “redwings.masugadesign.com"and BOOM…it works. I’m real excited about getting this to work.
As to your last post…I’m taking baby steps, and I see this as a small victory! I’ll try “the next level” next time.
#19 / Jun 11, 2008 4:42pm
slapshotw, thanks for your “parking” suggestion. I just did that for this client’s site, and it seems to be working perfectly. Now I’ll actually have everything in the exact directory it needs to be in when we go live, and like you said we’ll just need to change the IP/nameservers of domain.com to point to the new server.
Cool!
#20 / Jul 14, 2008 3:15pm
Anyone have an idea why a client might be getting a “server error” when trying to view the dev site I’ve set up as outlined above? I’m positive they’re trying to check the site from their office - so my guess is some kind of DNS error.
We have an A record for “dev.sitename.com” pointed to the new server (again, exactly as outlined above in this thread: dev subdomain is parked on the “sitename.com” account that is set up on this server) and it seems to be working fine for everyone except the one person from their organization that needs to review the site.
Thanks.