[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cobalt-users] Re: looking at a site before domain is transferred
- Subject: RE: [cobalt-users] Re: looking at a site before domain is transferred
- From: "Carrie Bartkowiak" <admin@xxxxxxxxxxxxxxxxxx>
- Date: Sun Oct 29 00:30:00 2000
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
I know that I can just type in the IP addy for the url... that's the main
beauty of a dedicated IP, lol... haven't found any other use for it. :) Is
there one?
Even without doing a reverse lookup in my DNS for the new site with its own
IP, the name will still resolve to the alpha-numeric domain name once it
hits my server. Then if I try to go to, say, IPaddress/~user it doesn't work
because it bounces over to the original server and looks for /~user. (god i
hope that made sense)
So tonight I had this situation. I have a client who's transferring from
Web2010. Her site is still active over there. I gave her her own IP and set
up her site, bonniewren.com in my Site Management. Then I went to the DNS
and put in two A records and an MX record for her, with *no* reverse lookup.
Then I went and added bonnie.allaboutchoice.com into my own site's record.
Finally, I went back to Site Management and changed her Site Settings from
bonniewren.com to bonnie.allaboutchoice.com.
So now the server is ready to receive requests for bonniewren.com. She can
get to her site by typing in her IP address. And if she wants to view a
directory, she can use bonnie.allaboutchoice.com/directory and she'll get
there rather than bouncing over to the site on Web2010.
When her name starts responding to my server, I'll just go in and add her
reverse record in the DNS(since she has her own IP) and change it back to
bonniewren.com in her Site Settings. And of course remove the subdomain in
my allaboutchoice.com settings.
Pain in the butt, but it works. :)
>I understand that you're saying you're going to assign ONE
>site to this IP number, right?
Yep, one site only on that IP.
>The test site trick I described is necessary ONLY when you're using
>name-based virtual hosts.
*nodding*
yep yep, I get that part.
So do any of the sites really need a reverse record whatsoever? (Besides
the server itself, I mean.)
Even the sites with a *dedicated* IP (one site per IP) don't need a reverse?
That would be pretty cool... one less step!
Carrie