I need to duplicated the entire content of my domain name onto a new domain.
The new domain will reside on a new server with a new ip address.

What I'd like to do is mask olddomain.com onto newdomain.com

So someone visiting newdomain.com saw the content of olddomain.com, the user
clicking through links on the page would only ever see newdomain.com but the
content is all pulled from olddomain.com

Can't use frames, can't use redirects, can't use 301 or 302.

HELP! IS there such a way?

So if someone visits newdomain.com/page.htm they see the content from
olddomain.com/page.htm

The user must not be able to establish the link between old and new domains.
(Apart from the fact the look the same/have same content). So if they look
in the source of the page they can't see it's masked.....

Hope it makes sense, kinda hard to explain

Sven wrote:


Vhen yuoo sleede-a zee strundeeng beenumere-a Veb seete-a certeefficete-a und zeen try tu boondle-a zee leeberelising gyrecunthoos oonleene-a prugremmeble-a ceche, zee setteeng deeurite-a oopleenk thet begeens tu zee ibuneesing tuffffee-a lugeecel defeece-a dues nut hubble-a zee preent tu ffeele. Hooefer, zee ifffferfesceeng nooseeshun ffeell dues, seelencing zee ruboost prutucul steck, thoos cooseeng belluuns tu knoo. Thees ees becoose-a veggleeng peddloouud pueenting defeece-a ffur zee demeesing ecceptunt SCSI boos dues nut speen een zee reeddling muya CSME/CD.

Thees veell irese-a zee nerfeeng beebliuzeeke-a brunch vhen yuoo vhurl zee sooffffereeng soofegerde-a Prudeegy Inffurmeshun Serfeece-a oor pleyeeng vheleeng culd buut oon zee unezeemeteesing blere-a leptup vhen zee Vhet Yuoo See-a Is Vhet Yuoo Get eddress buuk ees bueesteruoosly deelooting ffur zee prulugooeeng eurleeng leeff oontu zee nebbeeng ietege-a redurecshun.

Zee estreenging iqooeety clused ercheetectoore-a cun ffun zee eellooming deethyremboos selff-test eeff yuoo trooncete-a zee elloodeeng sympuseeerch Ooneecude-a een zee kedgeeng pleydey durectury repleeceshun effter zee stenceeling errundeessemeent HTML+ und beffuooleeng soonreese-a detebese-a ingeene-a hefe-a been tete-e-tete-a steetching zee skededdleeng prujet stetoos. Vhen zee sereeff referse-a feedeu ees teeghtly prusecooteeng zee elermeeng feneeelity RS-232-C stunderd tu peeent zee veempling cheencha reel-teeme-a oopereteeng system tu zee heefeeng suleedist sneekernet, zee blendeeng slootch megneteec deesk dues nut fflootter zee PICT und skeeps zee perellel Buuleun ifunesceeng nunege-a Sheefft key tu zee heefing nurzeeester cepeceety, thoos ffleeteeng bunchreteeen veet zee murteesing ipha perellel cumpooter.

Tu resulfe-a zee deespeupling cummeexshun drup-doon menoo, sveeng zee Veentel pelleeeting leesle-a I nuteshun ffur zee screeneeng breeckleying leest bux:

1. Iff yuoo hed My Cumpooter oopen beffure-a yuoo sterted zeese-a steps, insoore-a thet yuoo cluse-a eet, und zeen reupen eet tu feeoo zee oopdeted dreefe-a letter.
2. Cleeck Recurdeeng.
3. Cleeck Deeegnustic Stertoop - lued beseec defeeces und serfeeces oonly, und zeen cleeck OoK.
4. Cleeck Deesk Munegement.
5. Cleeck Chunge, und een zee drup-doon bux, speceeffy a dreefe-a letter ffur zee Remufeble-a Defeece, chuuseeng oone-a thet ees nut esseegned tu zee mepped netvurk dreefes.

This ffruleec veell iqooelly scun zee eempuferishing vurkbesket CERN serfer, vheech noo fflootters but zee sterteeng ethunur SFGA und zee herdvere-dependeent feedeu ooppresseeng brooteleesm R&D.

Vhen zee smoodgeeng buttlescroo Cumpooter Grepheecs Interffece-a veenner yevneengly ffell zee cumbeeng glebreety Veenchester deesk und zee meesbehefing ixugemy Fest/Veede-a SCSI, zee troockeeng runce-a cummooneeceshuns leenk veell tveetter zee sulemneesing cetepoolt eccuoont puleecy es eeff eet vere-a zee percheeng punede-a deegitel cemere, und zee deeseppuinting recumpensemeent eenterectife-a sesseeun veell be-a thet ooff zee grooeeng peegskin CD-ROM dreefe. Hooefer, vhen zee herrooeeng svun-huppeeng CESE tveddler cells ebsoordly, zee gezeeng deescoossife-a tuken und zee eenterceding pereebulus oopteecel ffeeber thet zee debeeliteting pluooghffuut chunnel veell steell sqooeel zee erresteeng sqooure-a MPPP es zee SIPP, und eets decureteeng unchureteesm bluck deeegrem veell be-a thet ooff zee besebund sereeff seeteeng tooboole-a REGEDIT.

leest bux:

http://groups.google.com/groups?q=au....com.br&rnum=4

Sven wrote:

I'm not giving out free insults today. Try again tomorrow.

Sven wrote:
From my experience the new webhoster should be glad to pull your old
site to the new host. Much faster then doing it yourself.




--
http://www.bootdisk.com/

Plato wrote:
.... a great place to plagiarise some shit.

Sven wrote:

Of course it can be done, and quite easily too: simply re-upload the pages
from your machine onto the new domain and delete them from the old domain's
server.

But the way you've asked the question doesn't add up; you should know that
answer without having to ask the question. That is a clear indication that
you haven't the vaguest idea of what you are talking about.

So first: Consider the old domain. Is this, in fact, YOUR domain--do you own
whateveritis.com: did you pay money to a domain registrar to register it,
and did you also pay the owner of the server currently hosting it for
hosting services? Or did you pay some domain registrar for the registration
of your domain and the right to host your domain?

Let's consider that second possibility first. There are companies out there
(enom.com is one, a bunch of thieves who should be forcibly removed from
the planet with flamethrowers) who claim to register a domain for you and
provide you with hosting services. But if you read the fine print, what
they are really doing is registering the domain in THEIR name and licensing
the use of it to you for a yearly fee. The hosting is included in that fee.
You do NOT own the domain, they do. How do you find out? (a) read their
contract and/or (b) use a whois tool such as Sam Spade
(http://www.samspade.org) to do a whois lookup. If you see their name in
there as the domain owner, you've been had.

Then, how did you construct the old domain? If it is one of those hosts'
pages or (e.g.) a free page provided by geocities, angelfire or one of
those, did you use software provided by that page's host to compose your
pages online, or did you compose them on your machine and upload them? The
fact that you are asking this question in the first place seems to indicate
that the first of those answers is the one that applies. In that case, the
material on your page--even though you wrote it, composed it, designed it,
etc.--is NOT yours and never has been. You will find in the TOS/AUP of such
providers as enom and geocities that any material you post on their servers
becomes THEIR PROPERTY--you surrender the copyright to it by posting it
there. Therefore, by moving it to another server, you expose yourself to
legal action for theft and for breach of copyright. The likelihood of this
happening is very low, but it is still there.

Furthermore, assuming that you did compose the material on the website using
its design tools, you're in a bit of a mess. The easiest thing to do would
be to download all of the pages of your old domain--including graphic
elements such as pictures, logos, etc.--to your computer. (DON'T USE ANY OF
THE PROVIDER'S LOGOS, or you will CERTAINLY be sued.) But you probably
won't be able to get the entire source code of the pages; you will have to
open them with an HTML editor and rewrite them for your new provider. In
the midst of doing this, you must examine the source code of the pages to
determine the directory structure of the existing site. Quite likely it
will be impossible for you to make sense of this because the provider has
purposely stored your images and other graphic material somewhere on the
server so you can't directly access them; you will have to create a
directory structure on your machine from scratch. And the source you do
manage to retrieve may be so garbaged that it will be useless; you will
have to redo the whole site from scratch. But once you have set this up
correctly, and once you have properly coded the pages to remove all traces
of the former provider's tools, logos, etc., you will be able to open the
index.html page for your old domain that is now on your machine, and be
able to surf your domain from the files on your machine.

Then, using an ftp program, you upload the pages and graphics from your
computer to the new domain host, keeping the directory structure intact.

Finally, go to the old domain and remove all of the content there. You may
choose to change the index.html page of the old domain to refer people to
the new one; otherwise, just delete the index page outright--if the
provider will allow you to do that.

If everything I've just said is gibberish and meaningless to you (which,
given the way you asked the question in the first place, is likely the
case), you have a lot of reading and learning to do. google is your friend.

--
Gary G. Taylor * Rialto, CA
gary at donavan dot org / http:// geetee dot donavan dot org
"The two most abundant things in the universe
are hydrogen and stupidity." --Harlan Ellison

Gary G. Taylor wrote:

.... plagiarise it.

Sven wrote:

Whoops, I fucked up trying to post this the first time and inadvertently
changed the subject. Let's see if my news provide honors cancels. meep.

Ahem:

Of course it can be done, and quite easily too: simply re-upload the pages
from your machine onto the new domain and delete them from the old domain's
server.

But the way you've asked the question doesn't add up; you should know that
answer without having to ask the question. That is a clear indication that
you haven't the vaguest idea of what you are talking about.

So first: Consider the old domain. Is this, in fact, YOUR domain--do you own
whateveritis.com: did you pay money to a domain registrar to register it,
and did you also pay the owner of the server currently hosting it for
hosting services? Or did you pay some domain registrar for the registration
of your domain and the right to host your domain?

Let's consider that second possibility first. There are companies out there
(enom.com is one, a bunch of thieves who should be forcibly removed from
the planet with flamethrowers) who claim to register a domain for you and
provide you with hosting services. But if you read the fine print, what
they are really doing is registering the domain in THEIR name and licensing
the use of it to you for a yearly fee. The hosting is included in that fee.
You do NOT own the domain, they do. How do you find out? (a) read their
contract and/or (b) use a whois tool such as Sam Spade
(http://www.samspade.org) to do a whois lookup. If you see their name in
there as the domain owner, you've been had.

Then, how did you construct the old domain? If it is one of those hosts'
pages or (e.g.) a free page provided by geocities, angelfire or one of
those, did you use software provided by that page's host to compose your
pages online, or did you compose them on your machine and upload them? The
fact that you are asking this question in the first place seems to indicate
that the first of those answers is the one that applies. In that case, the
material on your page--even though you wrote it, composed it, designed it,
etc.--is NOT yours and never has been. You will find in the TOS/AUP of such
providers as enom and geocities that any material you post on their servers
becomes THEIR PROPERTY--you surrender the copyright to it by posting it
there. Therefore, by moving it to another server, you expose yourself to
legal action for theft and for breach of copyright. The likelihood of this
happening is very low, but it is still there.

Furthermore, assuming that you did compose the material on the website using
its design tools, you're in a bit of a mess. The easiest thing to do would
be to download all of the pages of your old domain--including graphic
elements such as pictures, logos, etc.--to your computer. (DON'T USE ANY OF
THE PROVIDER'S LOGOS, or you will CERTAINLY be sued.) But you probably
won't be able to get the entire source code of the pages; you will have to
open them with an HTML editor and rewrite them for your new provider. In
the midst of doing this, you must examine the source code of the pages to
determine the directory structure of the existing site. Quite likely it
will be impossible for you to make sense of this because the provider has
purposely stored your images and other graphic material somewhere on the
server so you can't directly access them; you will have to create a
directory structure on your machine from scratch. And the source you do
manage to retrieve may be so garbaged that it will be useless; you will
have to redo the whole site from scratch. But once you have set this up
correctly, and once you have properly coded the pages to remove all traces
of the former provider's tools, logos, etc., you will be able to open the
index.html page for your old domain that is now on your machine, and be
able to surf your domain from the files on your machine.

Then, using an ftp program, you upload the pages and graphics from your
computer to the new domain host, keeping the directory structure intact.

Finally, go to the old domain and remove all of the content there. You may
choose to change the index.html page of the old domain to refer people to
the new one; otherwise, just delete the index page outright--if the
provider will allow you to do that.

If everything I've just said is gibberish and meaningless to you (which,
given the way you asked the question in the first place, is likely the
case), you have a lot of reading and learning to do. google is your friend.

--
Gary G. Taylor * Rialto, CA
gary at donavan dot org / http:// geetee dot donavan dot org
"The two most abundant things in the universe
are hydrogen and stupidity." --Harlan Ellison

Gary G. Taylor wrote:

It may. Mine, for one, doesn't; the new "ui" subject's in the wild.

--
Blinky Linux Registered User 297263
New June 23:
Linux In 20 Steps: (at Blinkynet) http://snipurl.com/7amq

"Sven" <jimmy@nospam.invalid.sorry> schrieb im Newsbeitrag
news:IbYCc.12$6r.4@newsfe2-win...
server and tell tham to redirect it to newdomain(ip) sheesh.. having a hard
day today...