Hi

I have two problem. Can you help me?

1) I have one server in the RackShack and with main domain COMPANY.COM - example - (DNS: ns.company.com and ns2.company.com)
I acquired more one server and I transferring my customers so that I can disactivate the current machine. But necessary to continue using the same DNS (changing only the IP).
How I edit my DNS of the new server so that I continue using the DNS (ns.company.com and ns2.company.com - modifying only the IPs) and without that the current server stops to function?

Example:
Today --> NS.COMPANY.COM IP: 207.44.238.2
NS2.COMPANY.COM IP: 207.44.238.3

I want use in new server:
NS.COMPANY.COM IP: 216.12.202.1
NS2.COMPANY.COM IP: 216.12.202.2

But the two servers need to continue functioning until I can point my new DNS in the main domain.



2) I asked for some additional IPs for my server but I do not know as to configure them.
How I make?
Which the command?

PS: I use the CPanel in my server


Thanks

Can't guarantee that I can help, as I'm a newbie really myself, but I just did this exact thing and the nice folks here helped me, so I'll try. The biggest thing is that you will need to change the IPs assigned to your ns. domains with your registrar. For instance, I use enom and this is a simple procedure of going to register dns and going to update a nameserver ip. I then changed each one(in my case, ns1.mydomain.com and ns2.mydomain.com) to the new IPs (I used two of the extras I requested from rackshack; neither being the first one on the server)and I went into my Cpanel and went to manage assigned nameserver ips(i think that is what it was called before i registered them; it is now) and I typed the name of the dns server that I wanted to add(ns1.mydomain.com for instance) and when I clicked add it allowed me to choose an ip from one on the server and walla, it works. Also, I did a few other things; not sure which ones really required; check into setting A server or something like that(I'm afraid I really don't know too much about all this) and I changed my hostname to main.mydomain.com. Not really sure what that does, but I didn't want it defaulted to a name that had nothing to do with me. I hope that helps; I would have left this to those who know more, but it didn't look like anyone was answering this one.

A couple of notes that I do know: you will have to change your ips with your registrar(who you got the name from, like register.com, etc.). If you can't figure out how, contact their customer service. It takes some time for the nameservers to change over-mine took about 16 hours to resolve here, but may be different in different locations. As far as having the other server up until you get switched: I THINK that you could leave the second nameserver on the old server until you get the first to working properly, but once it resolves, it will open on the ns1(i think all of the time? anybody no better?) if ns1, or whatever you named your first name server, is up. Otherwise, it would go to the next nameserver(ie ns2). I have thought about doing something like this, but have never tested it-not sure, but I think it would work-leaving my ns2 on an ip on my old sys and changing the ns1 ip to one of those on the new server and then setting up the new server while the wait is going on for the nameserver ip to resolve. It would still be going to the first servers before it resolved, so there wouldn't be a huge problem there and, after it resolved, I think that you could delete the nameserver on the new server if it didn't work and figure out what you had done wrong and then, when the problem was fixed, just re-enter it to test again. In the interim, if I am correct, you would still be able to see the data on old sys by the ns2 if the ns1 had no up server to attach to. This is only my little bit from what little I know; please don't hold me to it. If you have the settings done properly in CPanel and already have the sites set up, it will just nicely switch over to the new server with no downtime as it dynamically switches IPs in the registry.....at least it always seems to for me. I hope I'm not telling you anything wrong here, but this part of the process went pretty smooth for me. The part that was hard for me was running a script to repair an error-one of the other nice members of the forum was nice enough to point me to a program called putty that made life much easier.