Best Way of "Mirroring" a Domain

[bladephoenix]

Here is the situation:

I want to register two domains: tomatographics.com & tomatoegraphics.com. I basically want tomatoegraphcis.com to forward to tomatographics.com. Tomatographics.com is to be hosted on a Fedora Core 4 Server which has a dynamic IP address. It will use a DYNDNS service to resolve to the correct IP address. I have asked the registrar if their domain forwarding option will forward www.tomatoegraphics/directory/file.htm to www.tomatographics/directory/file.htm. It will not. It will also not forward ftp.tomatoegraphics.com to ftp.tomatographics.com. It will only forward www.tomatoegraphics.com to www.tomatographics.com. It is possible to achieve the desired effect using IP forwarding instead of domain forwarding, but since it is a dynamic IP, that would be very difficult. IP forwarding will also not forward ftp.tomatoegraphics.com to ftp.tomatographics.com.

So, I suppose I can resolve this problem by buying another DYNDNS service for an additional $25. In that case, both domains would have a DYNDNS account and both would forward to the same IP. However, I was told this had two negative consequences: 1) Since the site will have a login page using https and SSL, the visitor might get a "invalid SSL certificate" error depending on whether he/she typed in the "real" domain name. I also heard there might be missing graphics and stuff, when using https and two domains names with the same IP. 2) Duplicate content penalty on search engines.

Is there a way I can:

1) get www.tomatoegraphics.com/directory/file.htm to forward to www.tomatographics.com/directory/file.htm.
2) get ftp.tomatoegraphics.com to forward to ftp.tomatographics.com.
3) somehow make it so there isn't the problem with invalid SSL certificate and missing graphics.
4) have both domains on the search engine.
5) avoid a duplicate content penalty.

I am open to any suggestion, but I was hoping for a cost-effective, minimal headache way of fixing this problem.

Thanks for any suggestions.

 

[Genx87]

I have only played with things like this before but when you register tomatoegraphics.com isnt it pointing to the same IP as tomatographics.com?

Cant you just have your start page redirect you to tomatographics.com?

 

[ITJunkie]

Also, is there any particular reason, other than cost, why you can't go with static IP's and avoid DYNDNS altogether?
It would greatly simplify what you are trying to accomplish.

 

[bladephoenix]

Originally posted by: Genx87
I have only played with things like this before but when you register tomatoegraphics.com isnt it pointing to the same IP as tomatographics.com?

Cant you just have your start page redirect you to tomatographics.com?

The registrar I has three options: 1) Specify your own name servers (as opposed to their own). 2) Point the domain to an IP 3) Point the domain to a URL.

I suppose I can get away with just point the start page, it wouldn't be the end of the world. Its only that when we tell people our domain, they might use the alternate spelling of tomato. When using HTTP, it will direct them to the "real" URL, however when people use FTP, I will keep getting calls about how they can't log in. Then I will have to ask them how they are spelling tomato. Then they will say, "I can reach your website using www.tomatoegraphics.com, why can't I reach ftp.tomatoegraphics.com", etc. Then I will have to go into a long bloated explaination. Most vistors to the site are not really technical, so I want to accomodate them to avoid repeated questions later on.

Originally posted by: ITJunkie
Also, is there any particular reason, other than cost, why you can't go with static IP's and avoid DYNDNS altogether?
It would greatly simplify what you are trying to accomplish.

Cost is part of the reason why no static IP. You see, the site is somewhat of a project of mine where I would like to do my own web/file hosting and have a little fun with that. I can switch to an ISP which offers static IPs (mine currently does not), but they are about 100USD/month -- that is > 2x the monthly charge I am paying now, and I really can't afford that. So yes, cost is the main reason, but not the only reason.

 

[EatSpam]

Originally posted by: ITJunkie
Also, is there any particular reason, other than cost, why you can't go with static IP's and avoid DYNDNS altogether?
It would greatly simplify what you are trying to accomplish.

Yeah... I always kind of shrug my shoulders when I see people running servers on a Dynamic IP. Most of the time, its not even allowed per the TOS. Its much easier just to get a static ip.

 

[bladephoenix]

Originally posted by: EatSpam

Originally posted by: ITJunkie
Also, is there any particular reason, other than cost, why you can't go with static IP's and avoid DYNDNS altogether?
It would greatly simplify what you are trying to accomplish.

Yeah... I always kind of shrug my shoulders when I see people running servers on a Dynamic IP. Most of the time, its not even allowed per the TOS. Its much easier just to get a static ip.

Funny, I was looking at the TOS, and there is no mention of the prohabition of servers. Only that if I exceed "reasonable" bandwidth, they have the right to terminate service. I've seen people use the service who download 10 GB/month and upload as much. It pikes me as somwhat as a curiousity, becuase I have never even exceeded 1 GB in either direction. So, it probably isn't a problem, as far as TOS is concerned, unless I start reselling their service, which isn't going to happen.

 

[LOFBenson]

I would recommend zoneedit.com for your DYNDNS service. I doubt you need more than their free account. Point all the subdomains to the same IP and then forward one web site to the other on your side (or use their webforward service but that might cost you $)should fix your problems.

 

[cmetz]

bladephoenix, first of all, why don't you go get your web site hosted somewhere else? Web hosting now is super cheap, and that will solve all the DYNDNS et al. kinds of problems right off the bat.

 

[JRock]

Its you just have to point the A records for those domains to the ip of the server. There is no "mirroring" involved. Just both domains point to the single ip address of that webserver. You can usually manage your DNS records through the registrar you signed up with. If not I would recommend you sign up www.dnsmadeeasy.com you can manage all your records. A, MX etc. just my .02

Also www.dnsstuff.com to lookup extisting records.