one domain 2 servers
 

how can I do this

I have a client with a live site wanting a new site... they want to keep old site live at host while new site is being built on new host...

this is from client

The existing website is hosted at 75.99.142.202. CNAME www and root of the domain point to that IP. The rest of the domain is at 65.254.248.204, including the WP. We can redirect www and the root domain to 65.254.248.204, but we need you to redirect any http traffic to 75.99.142.202. His current site uses ASP and we do not use it on our new server. Once the your site is complete, we can remove the redirect.


this is above my pay grade .... simple fixes?

I don't understand a lot of what you are wanting, but I do know you can host the main domain on one server, and a sub-domain on a different server. Perhaps you can build the new site on the sub domain/new server, and when all is complete, move the domain name to the new server or have the host put an auto re-direct on the original server site to the sub-domain.

You change the A name for the sub to point to the original DNS. There is an article that describes the steps: http://css-tricks.com/put-a-subdomai...ferent-server/

Another easy, temporary, solution is to put the new site on your new server and assign the domain to an IP in Apache only. Then use your local computer's HOSTS file to point the domain to that IP. Switching back and forth is as easy as commenting out the IP line in your local computer's HOSTS file.

explain this sir... I'm on mac...

this is way above my pay grade I just design , build and implement all the nice programs and plugins that you geniuses make

Just build their site on the new host (using the ip address) - when it is complete - redirect the domain to the new host.

I don't understand why you are over complicating it?

this is what I wanted to do....

Zoneedit is pretty easy stuff.
I use it to manage domains that are not hosted anywhere etc...
I think I've used it for about 10 years(lost count).
Seems very stable, never had a problem.

http://www.zoneedit.com/

DD: you have a couple of options presented in the thread here (eta, I see others now too)

1. Just setup the new site on an IP from your new server and access it via the IP for preview and testing purposes. Assuming your internal links are relevant paths versus full http links, you should be able to preview it without issue.

2. Assign the new site to an IP on the new server. Follow the link DamianJ provided and add a new line to your HOSTS file with the IP and the domain you want to resolve on the IP, on the same line.

Your HOSTS file can override the IP's existing on which existing sites resolve. You could edit your HOSTS file and put GFY's IP in it and assign the IP to Yahoo.com. Then anytime you typed in gfy.com in your browser, you'd end up on Yahoo.com.

Once you are satisfied the new site is doing exactly as you want, edit the DNS for it at your registrar, and then the new site will replace the old one. (If you used the HOSTS file method, then you'll need to remove the hosts entry you added).

personally I like the first option then I'm not fond of changing hosts file on here even tho I've done it before if I remember when I was installing nats years ago......

can I do wp at the ip level ?

thanks again guys for help and suggestions

DD: you can do it at the WP-CONFIG level so long as you are using an IP or a subdomain (you can't put in the actual real domain since it resolves somewhere else, unless using the HOSTS file method, then certainly you could use the actual domain.) Simply follow the directions on the link below and put the new IP where the new site and install wordpress there.

http://codex.wordpress.org/Changing_The_Site_URL

Just a note about that method - If you are using a WPMU install to use subdomains it could get tricky...

A vanilla install will be fine.....

you can buy some other extension (like .info or .net) and build the site there... Limit access per IP to prevent others for accessing the site while you work...

Keep it simple, keep domain.com where it is, and host dev/domain.com on other host.

Once ready to go live with new site, move domain.com to new location.

Did you make up your mind on how your doing this yet? If not shoot me an email david <at> phasicllc.com

I think we got it.. ill post back tomorrow the result of how we did it...

thanks again everyone

Use Haproxy and just choose port 80 and 443 to be proxied to the old host