Tried to set up private nameservers for a domain registered at GoDaddy, and got this message from GoDaddy:

The registration of NS1.MYSITE.COM has FAILED.

The IP you requested for this name server was:

xxx.xxx.xxx.xxx

Error: Parent domain has non-active status

The www for the MYSITE.COM is currently virtually hosted (not at GoDaddy).

The nameservers are set up on a dedicated server at another provider, and are active. The NS1 IP was correct as entered.

The www for MYSITE.COM is not registered with the new nameservers. It should continue to be hosted where it is, using that provider's nameserver. The NS1/NS2.MYSITE.COM is for use at this point only by other domains that I have.

Is there something I'm missing in creating the nameservers?

Is the Ip address of the nameserver you are creating unique or is it a shared ip?

NS1/NS2 are first and second assigned IPs of the block of IPs that comes with the dedicated server. This is all set up through cPanel/WHM.

Error: Parent domain has non-active status

Does godaddy require you to unlock the name before you make this kind of change?

Yes. You just click to unlock, do the changes, relock. Which I did.

One of the many support people who haven't been able to solve this suggested that the NS's have to be registered with the nameservers where the main www. account is hosted?

Here's the situation I'm trying to get it to, as clear as I can make it:

1. MYSITE.COM registered at GoDaddy. (Registered years ago)

2. MYSITE.COM is pointed to NS1/NS2.PROVIDER-ONE.COM, where it is hosted on a virtual domain account. (This is current, been active for years.)

3. Set up a dedicated server at PROVIDER-TW0, which they designated as HOST.MYSITE.COM (this host is NOT registered, doesn't resolve). (Done a few days ago)

4. Attempting to create NS1/NS2.MYSITE.COM at PROVIDER-TWO. Thes NS's to be used to resolve other domains, but NOT for the MYSITE.COM web account, which remains pointed to and hosted by PROVIDER-ONE, as it is right now. (This is The Problem)

The maybe unusual thing is that I'm not planning to use the private nameservers to resolve the site for the parent DOMAIN (MYSITE.COM) they're on. But I'm told this is OK to do.