DNS transfer from shared to VPS

[jboulton]

I am currently transferring websites from a shared hosting plan using DA to a VPS using DA. I change the DNS settings for the domain name to the VPS host then I change the NS records at the shared hosting server to point to the new VPS records. Ex:

domainname1.ca. NS ns1.vpshost.ca.
domainname1.ca. NS ns2.vpshost.ca.

Things were working then I moved over 3 new websites and made the DNS changes. I can't reach any site now. I don't think adding DNS records on the shared server would reset the other DNS records which have propagated?

Any ideas? Thanks.

 

[nobaloney]

You can't resolve the issue even though you know the domain names but you expect us to know the answer without knowing the domain names?

I suppose I can always reply Something in DNS is broken. You don't give enough information to know what.

We need to know the nameserver names, the domain name, and the IP# on both servers, if we're to be able to help.

Jeff

 

[jboulton]

The shared host ip is: 74.63., ns609a.private.com and ns609b.private.com. This is where I have my resellers account setup with my domain reactive.net.

The VPS ip is: 67.231 - ns1.reactive.net, ns2.reactivenet. I have admin DA and a resellers account setup where I am moving the shared hosting sites over too.

Two domains on the VPS which are not resolving for me:
www.pense.ca and http://www.clive.ca

I have:
pense.ca. NS ns1.reactive.net.
pense.ca. NS ns2.reactive.net.
clive.ca NS ns1.reactive.net
clive.ca NS ns2.reactive.net
ns1.reactive.net. A 67.231.
ns2.reactive.net. A 67.231.
in the DNS records on the shared hosting account.

I have set the DNS records for both domain names to ns1.reactive.net and ns2.reactive.net.

Yesterday the domains resolved then today they are not working (I did not change any settings). I'm not sure what I'm doing wrong. I would appreciate any suggestions. Thanks.

 

[yonatanp]

you have to create your own nameservers

login to your http://www.enom.com domain control panel,
over there, you have to register your domain as a name server , create ns1 and ns2 records which will point at your VPS ip addresses,


by the way, for the act of good order, get yourself a secondary IP address for ns2 , its kinda worthless pointing both ns's to the same IP ( even to the same physical machine , but that's something else ).

your current setup means you are still depending on your old hosting account, which is not a good idea, let your VPS manage your named servers.

 

[jboulton]

I have several accounts on the shared host to move over to the VPS. I was hoping to do this slowly and make sure they work - one by one. After I moved the sites over I was going to change reactive.net nameservers over to ns1.reactives.net and ns2.reactive.net.

I was hoping to add the DNS records to reactive.net - shared server as I moved the websites over.

Is this possible?

I added
ns1.reactive.net. A 67.231
ns2.reactive.net. A 67.231

to the DNS on the shared server.

Thanks for the tip on the ip's!

 

[jboulton]

The other question - if I did move over reactivedesigns.net to the VPS and I did not have all the sites hosted on the shared account moved over to the VPS account would they still work?

 

[nobaloney]

No matter where they're hosted, your nameservers (ns1.reactive.net and ns2.reactive.net) MUST hold the domain names AND the IP#s where you're hosting the live sites.

If you want to move sites slowly, but move the DNS nameserver IP#s only at the last minute, then you can simply update the DNS at the old location, to point the moved domains to the new IP#s.

Jeff