co.za

[cavedog]

Right I want to move to a new hosting provider.

How can I update the name servers?

The reason I'm asking that is cause in cpanel I tried to add the domain and it says that the name servers are not pointed to the dns of the server.

But we know that co.za requires the domain have valid name servers before you can update it.

So How can I change them?

My new host doesn't seem to understand this and even me cause co.za is THE ONLY registrar that does this.

 

[texo]

If cpanel is giving you the error message, then it is probably because that server is not setup to "Allow Creation of Parked/Addon Domains that resolve to other servers"
You will need to ask your host to change that setting, in the "Tweak Settings" section of WHM.

As you've said, you will need to create DNS entries for the domain on the new server before Uniforum will allow you to update the domain to point to that server.

 

[RSkeens]

Another option would be to have the DNS records on the old provider changed to point to the new provider, but you may experience longer site content and e - mail unavailability while you await the new provider's DNS to get updated.

 

[kissingmybbgoodbye]

Get an account with http://www.editdns.net

 

[cavedog]

Thanks for the replies. Let me see what I can do to get this working.

 

[guest2013-1]

Another option would be to have the DNS records on the old provider changed to point to the new provider, but you may experience longer site content and e - mail unavailability while you await the new provider's DNS to get updated.

huh?

No...?

When you move providers that (obviously) have you on their DNS and need to change the .co.za registrar to new DNS servers, usually what I do is to move my site and setup my email on the new provider. Once that's done I point the site IP address and MX records' IP address (which is usually just the mail A host record anyway) to the new IP ranges. *this is instant*

Then once i'm happy everything is working 100%, and I pulled off any mail from the old server that might have landed as some mail servers caches the IP for your MX records for a while, I put in the request to change the DNS servers. I use http://www.editdns.net myself because it's my own DNS servers an independent of any host. So i'm not bound by my own laziness if I choose to move providers because of the co.za crap.

Once the ticket goes through and the DNS servers change, there will still be NO downtime for you (not even prolonged, hence my "huh?" to this quoted reply) as it's just switching to another server with the same records on it, so the internet will always know where you are, even if they're looking at the old DNS server for a while after the update.

 

[RSkeens]

huh?

No...?

When you move providers that (obviously) have you on their DNS and need to change the .co.za registrar to new DNS servers, usually what I do is to move my site and setup my email on the new provider. Once that's done I point the site IP address and MX records' IP address (which is usually just the mail A host record anyway) to the new IP ranges. *this is instant*

Then once i'm happy everything is working 100%, and I pulled off any mail from the old server that might have landed as some mail servers caches the IP for your MX records for a while, I put in the request to change the DNS servers. I use http://www.editdns.net myself because it's my own DNS servers an independent of any host. So i'm not bound by my own laziness if I choose to move providers because of the co.za crap.

Once the ticket goes through and the DNS servers change, there will still be NO downtime for you (not even prolonged, hence my "huh?" to this quoted reply) as it's just switching to another server with the same records on it, so the internet will always know where you are, even if they're looking at the old DNS server for a while after the update.

He can't create the account in cPanel, the control panel of his host. Why? Because the DNS for the domain name is not pointing to the host's servers. When it does, it will allow the account creation and the name server records at the new provider for the .co.za update to go through.

Also, changing a zones's A and MX records are NOT instant because they are cached on external servers. You can read up on TTLs from a Google search, they are there for a reason.

To explain your huh: He changes the records on the old provider tothe new provider, then waits for the new provider's DNS to recognise the change before he can even create the account. During that time certain mail and traffic will be directed to the new provider and will not be accepted. Finally he can then change the name server records over at UniForm. I hope that explains it.