Re: One web server, multiple domains; a slight twist

On Wed, 29 Oct 2008 19:09:47 -0700, sb5309 wrote:

The question arises out of curiosity, from a recent attempt by a
temporary staff to transfer a domain from one web server to another web
server; he forgot to change the DNS record (the company is dealing with
2 ISPs). Later I was asked to FTP somes files to a server, which end up
in the "old" server.

Please do not mix DNS records, domain creation and Virtual Host
management on a LAMP server.

zzz.com is resolved by at least two name servers. Without control over
the domain, you can not change the name servers. Without control over the
name servers, you can not change the IP addresses for the hosts on the
domain.

Having control over the resolver of your client, you can however make
your client and software running on the client, access the new host.

A line in /etc/host like this:

201.100.100.200 www.zzz.com zzz.com

will make sure your client will access the new server, as if the DNS
records where updated. Please restart your browser and FTP client.

Of course I can go to the control panel of the other ISP and transfer
files using its file manager.

Out of the blue, I wonder whether it is possible to access the other
server using IP address, thereby avoiding a DNS look-up (which will
end-up in the "old" server). Off my head, I believe it is possible, just
that what is the form of this command.

The answer "yes" is sufficient; I shall experiment a bit myself. Thanks.

Now you mix FTP and HTTP, spiced with Virtual Host configuration... Both
the old, and the new server has a target directory for uploading it's
HTTP served files. If you can find and address this directory, it's
surely possible to FTP files into this directory, using IP address and
the proper path.

The same goes for HTTP requests, but the path is probably not the same as
when using FTP.

Feel free to experiment...

--
Regards/mvh Joachim Mæland

If everything seems under control, you're just not going fast enough.
-Mario Andretti
.

Quantcast