Forum Moderators: phranque
I have recently created a site, registered the domain name and put it up live. Let's call this Site A and it's currently online and working perfectly.
To FTP to this site I've used the FTP details (an IP address) sent to me by the hosting company in their welcome email. I pointed my domain name (bought through godaddy.com) to their hosting by using the provided DNS entries as listed in their welcome email.
Now, my client had an old site 'Site B', different URL, not developed by me, which he wants to re-direct to this new site. So, someone enters the URL of Site B into their browser, they get brought to Site A seamlessly. I contacted the ISP in question about redirecting to the new site.
I thought they would need the DNS entries of my Site A to redirect Siet B but they told me they needed an IP address for the redirect to work.
I've a feeling I'm missing something obvious here but I can't figure out which IP address to provide them with.
Like I said I use an IP to FTP to Site A so I sent them that. Lo and behold Site B is now not working, not redirecting, just giving an error. So obviously I sent the wrong IP address.
So, what IP do I send them and how do I find it? This is probably really obvious but I'm not getting it. Doing a PING to Site A obviously produces an IP address, is that what I should send them? Is it normal to require *only* an IP address to get a redirect working, suerly being able to enter www.sitea.com as the redirect would be easier.
Any help anyone?
Thanks!
www.siteA.com currently points to www.siteA.com/apage.htm
You need to set www.siteB.com to point to www.siteA.com/apage.htm with domain forwarding.
I hope this explains it clearly. I'm not so good at explaining stuff, I just know how to do it.
Ska
When someone navigates to siteB, siteB's DNS server redirects the user to siteA's IP addres. When SiteB's DNS server redirects the traffic from SiteB to SiteA the header information is not updated. The header still has the URL for siteB.
Web servers that host many sites look at the URL in the header of a an IP packet to serve up the correct site, serverA has to look at the URL embedded in the header of the packets requesting service (including those from siteB). When the redirected traffic arrives at the IP address of siteA it still has the URL for siteB in its header.
To fix the problem you need to get the web host of Site A to add siteB's domain name to its web server. Once SiteB's domain names has been added to the web server, the web server will see siteB as a valid domain and find the corect pages. Right now ServerA doesn't recognise SiteB's URL and so returns and error.
Some web hosts will do this for free, others will not. Many large cheap hosting companies will ask you to pay as though you were moving siteB.
If you can't get the hosting company that host siteA to work with you there are ways you can redirect a site using PHP. The way you are proceeding will work best.
Custodian
