Well, except that we _don't_ own it. Our partner registered the name (I work for a startup with 2 major partners) and so they own it right now. Rather than transfer ownership of the domain (something that I want do to in the long-term) we just wanted to change the DNS pointers for now. He seems to think that simply switching the A record to the proper IP addy will happen instantaneously, while the propagation for an NS change will take from 3 days to a week. Since the site is currently live both on his servers and mine, I don't see a problem with the propagation, but this is (cue patriotic music) the IT/DNS guy for a Fortune 500 company with 20,000 employees in 82 locations worldwide blah blah blah blah... so he thinks he is king sh!t. That's why I wanted to know if there were technical reasons why this is not a good idea.

>Hmmm. you own the domain name, right?  Simply log into the account manager
>where the domain is registered (network solutions, register.com, godaddy)
>and change the NS yourself.  
>
>- Matt Small
>
>  _____  
>
>From: Marwan Saidi [mailto:[EMAIL PROTECTED]
>Sent: Thursday, August 26, 2004 4:44 PM
>To: CF-Community
>Subject: DNS / Hosting Question
>
>Ok, DNS, BIND, and all that are not my strong point. Basically, we have a
>site that is hosted at one of our partners. We want to move everything off
>of partner resources and to our own host. I want the partners to change the
>NS of our domain to point to our host. They want to simply change the alias
>record to point to the IP of the site at our host.
>
>I don't know much about all of this, but couldn't this possibly have some
>repercussions with something? Would email appear to be being relayed? Would
>there be a problem with SSL and certificates? Jochem?
>  _____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Reply via email to